Skip to main content
Glama
IBM

chuk-mcp-geocoder

by IBM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to chuk-mcp-geocoder

No user-submitted related servers found.

    Related Servers

    • geocode-mcp

      danishashko
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for geocoding, reverse geocoding, place/POI search, and distance calculation using OpenStreetMap Nominatim, with no API key required.
      47 npm
      1
      MIT

    • overpass-mcp

      Rusty0508
      A
      license
      A
      quality
      C
      maintenance
      MCP server providing structured access to OpenStreetMap data through Overpass and Nominatim APIs, enabling geocoding, nearby place searches, element queries, and tag counting without API keys.
      7
      MIT

    • mcp-photon

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      A geocoding MCP server that converts place names to coordinates and coordinates to place names using OpenStreetMap data.
      2 npm
      MIT

    • Geo MCP Worker

      Kerry1020
      A
      license
      Not graded
      quality
      C
      maintenance
      Free geospatial MCP server for AI agents, providing geocoding, reverse geocoding, POI search, and route planning using OpenStreetMap data via Nominatim, Overpass, and OSRM.
      1
      GPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: forward geocoding, reverse geocoding, batch, admin boundaries, bounding box, distance matrix, route waypoints, nearby places, and server info tools. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern and are descriptive of their function. The naming is uniform and predictable, aiding agent selection.

    Tool Count5/5

    With 10 tools, the server is well-scoped for a geocoding service. Each tool serves a specific need without being excessive or insufficient.

    Completeness5/5

    The tool set covers the full lifecycle of geocoding operations: forward/reverse, batch, administrative boundaries, distance calculations, route planning, and status/info. No obvious gaps for its domain.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources