Skip to main content
Glama
BACH-AI-Tools

Geocoding By API Ninjas

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Geocoding By Api Ninjas MCP Server

English | 简体中文 | 繁體中文

用于访问 Geocoding By Api Ninjas API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

  3. 🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器

  4. 🔍 搜索或找到本服务器（bach-geocoding_by_api_ninjas）

  5. 🎉 点击 "安装 MCP" 按钮

  6. ✅ 完成！即可在您的应用中使用

EMCP 平台优势：

  • ✨ 零配置：无需手动编辑配置文件

  • 🎨 可视化管理：图形界面轻松管理所有 MCP 服务器

  • 🔐 安全可靠：统一管理 API 密钥和认证信息

  • 🚀 一键安装：MCP 广场提供丰富的服务器选择

  • 📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: Google Maps Geocoding MCP Server

简介

这是一个 MCP 服务器，用于访问 Geocoding By Api Ninjas API。

  • PyPI 包名: bach-geocoding_by_api_ninjas

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-geocoding_by_api_ninjas

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（uvx 会自动安装并运行）
uvx --from bach-geocoding_by_api_ninjas bach_geocoding_by_api_ninjas

# 或指定版本
uvx --from bach-geocoding_by_api_ninjas@latest bach_geocoding_by_api_ninjas

方式 2: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-geocoding_by_api_ninjas

# 运行（命令名使用下划线）
bach_geocoding_by_api_ninjas

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bach-geocoding_by_api_ninjas": {
      "command": "uvx",
      "args": ["--from", "bach-geocoding_by_api_ninjas", "bach_geocoding_by_api_ninjas"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件 claude_desktop_config.json:

{
  "mcpServers": {
    "bach-geocoding_by_api_ninjas": {
      "command": "uvx",
      "args": ["--from", "bach-geocoding_by_api_ninjas", "bach_geocoding_by_api_ninjas"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

可用工具

此服务器提供以下工具:

v1geocoding

API Ninjas Geocoding API endpoint.

端点: GET /v1/geocoding

参数:

  • city (string) 必需: City name.

  • state (string): US state (for United States cities only).

  • country (string): Country name, 2-letter ISO country code, or 3-letter ISO country code.

v1reversegeocoding

API Ninjas Reverse Geocoding API endpoint.

端点: GET /v1/reversegeocoding

参数:

  • lat (number) 必需: Latitude coordinate.

  • lon (number) 必需: Longitude coordinate.

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

此服务器由 API-to-MCP 工具生成。

版本: 1.0.0

Available Tools

2 tools
v1geocodingD

API Ninjas Geocoding API endpoint.

ParametersJSON Schema
NameRequiredDescriptionDefault
cityYesCity name.
stateNoUS state (for United States cities only).
countryNoCountry name, 2-letter ISO country code, or 3-letter ISO country code.

TDQS

D1.7/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description does not reveal any behavioral traits such as rate limits, authentication needs, error handling, or what the tool returns (e.g., coordinates). It lacks essential details for a tool that likely performs external API calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single phrase 'API Ninjas Geocoding API endpoint', which is overly concise to the point of under-specification. It fails to front-load key information about the tool's function, making it inefficient for quick understanding. While brief, it lacks substance and does not earn its place as a helpful description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a geocoding tool (likely involving external API calls and coordinate outputs), the description is incomplete. No annotations exist, and there is no output schema, so the description should compensate by explaining return values or behavior, but it does not. It fails to provide enough context for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with clear parameter descriptions (e.g., 'City name', 'US state (for United States cities only)'). The description adds no additional meaning beyond the schema, but the schema is comprehensive, so the baseline score of 3 is appropriate as it adequately documents parameters without extra value from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'API Ninjas Geocoding API endpoint' restates the tool name 'v1geocoding' and adds minimal context (the provider name). It does not specify what the tool does (e.g., convert addresses to coordinates), making the purpose vague. It distinguishes from the sibling 'v1reversegeocoding' only by name, not by functional difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description does not mention the sibling tool 'v1reversegeocoding' or any other context for usage. There is no indication of prerequisites, constraints, or typical scenarios for application.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

v1reversegeocodingC

API Ninjas Reverse Geocoding API endpoint.

ParametersJSON Schema
NameRequiredDescriptionDefault
latYesLatitude coordinate.47.6062
lonYesLongitude coordinate.-122.3321

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It doesn't describe whether this is a read-only operation, what kind of data it returns (e.g., address components), potential rate limits, authentication requirements, or error conditions. The description is essentially a label rather than behavioral guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise - a single phrase that identifies the API service. While it's under-specified in terms of content, it's not verbose or poorly structured. Every word earns its place by identifying the provider and endpoint type.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's purpose (geospatial conversion) and the absence of both annotations and an output schema, the description is insufficient. It doesn't explain what the tool returns (address information), doesn't provide context about the API provider's limitations or requirements, and doesn't help an agent understand how to interpret results. For a tool with no structured behavioral hints, the description should do more heavy lifting.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with clear documentation for both 'lat' (latitude coordinate) and 'lon' (longitude coordinate). The description adds no parameter information beyond what's in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'API Ninjas Reverse Geocoding API endpoint' states the tool's general purpose (reverse geocoding) but is vague about what it actually does. It doesn't specify the verb (e.g., 'convert', 'look up', 'retrieve') or the resource (e.g., 'address', 'location details'), and doesn't distinguish it from its sibling 'v1geocoding' which presumably does forward geocoding. The description is functional but lacks specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling tool 'v1geocoding' or explain that reverse geocoding converts coordinates to addresses while forward geocoding does the opposite. There's no context about prerequisites, limitations, or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.0
    • First observedv1geocoding
    • First observedv1reversegeocoding
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.5/5.0
Disambiguation5/5

The two tools have perfectly distinct purposes: one converts addresses to coordinates (geocoding) and the other converts coordinates to addresses (reverse geocoding). There is no overlap or ambiguity between them, making it impossible for an agent to confuse their functions.

Naming Consistency5/5

Both tools follow a consistent naming pattern with 'v1' prefix and descriptive suffixes ('geocoding' and 'reversegeocoding'). They use the same style (lowercase with no separators) and clearly indicate their functions, ensuring predictability and readability.

Tool Count2/5

With only 2 tools, the server feels thin for a geocoding service, as it lacks operations like batch processing, validation, or additional geospatial queries. While the core functions are covered, the limited scope may hinder more complex agent workflows that expect broader capabilities.

Completeness3/5

The server covers the basic bidirectional conversion between addresses and coordinates, but there are notable gaps such as missing batch operations, address validation, or support for different coordinate formats. This limits the surface for handling varied geocoding tasks, though agents can still perform fundamental lookups.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Geocode MCP Server

    X-McKay
    A
    license
    A
    quality
    C
    maintenance
    Provides global geocoding capabilities to convert city names and addresses into latitude/longitude coordinates using the free OpenStreetMap Nominatim API.
    1
    5
    MIT

  • Google Maps Geocoding MCP

    kevinwuhoo
    A
    license
    A
    quality
    D
    maintenance
    Enables LLM clients to convert addresses to coordinates (forward geocoding), coordinates to addresses (reverse geocoding), and lookup Google Place IDs using the Google Maps Geocoding API with support for multiple languages and advanced filtering.
    3
    18
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/bachai-geocoding-by-api-ninjas'

If you have feedback or need assistance with the MCP directory API, please join our Discord server