Skip to main content
Glama
fastmcp-me

chuk-mcp-geocoder

by fastmcp-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to chuk-mcp-geocoder

No user-submitted related servers found.

    Related Servers

    • chuk-mcp-geocoder

      IBM
      A
      license
      A
      quality
      F
      maintenance
      An MCP server providing geocoding and place discovery services via Nominatim and OpenStreetMap. It enables users to perform forward and reverse geocoding, extract bounding boxes, and find nearby places or administrative hierarchies.
      10
      Apache 2.0

    • OpenStreetMap MCP Server v2

      ogSINGH
      A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to geocode and reverse geocode places, find nearby points of interest, search categories within an area, get turn-by-turn routing, suggest meeting points, and analyze neighborhoods, commutes, schools, EV charging, and parking through OpenStreetMap data services. It also serves place and map tile resources over stdio, SSE, or Streamable HTTP transports.
      12
      MIT

    • mapsi-mcp

      algolayertechnologies
      A
      license
      A
      quality
      D
      maintenance
      Geospatial API tools for AI agents — geocoding, reverse geocoding, routing, isochrone, distance matrix, static maps, H3 hexagons, elevation, GPS map-matching, point-in-polygon, address normalisation, timezone lookup, and batch geocoding. Built on OpenStreetMap infrastructure. Cost-effective alternative to Google Maps API.
      18
      24 npm
      MIT
    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

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have distinct purposes, but bbox_from_place and geocode overlap slightly (both take place names) and batch_geocode is a batch version of geocode. Descriptions clarify differences, so agents can likely distinguish them.

    Naming Consistency3/5

    All names use snake_case and are descriptive, but they mix verb phrases (geocode, reverse_geocode), noun phrases (geocoder_status, admin_boundaries), and compound expressions (bbox_from_place, nearby_places). No single consistent pattern.

    Tool Count5/5

    10 tools is appropriate for a geocoding server, covering forward/reverse geocoding, batch operations, bbox extraction, nearby places, admin boundaries, routing, and distance computation without being excessive.

    Completeness4/5

    Covers core geocoding operations well. Minor gaps: no explicit search by category or type, but nearby_places and admin_boundaries provide related functionality. The retry workflows in descriptions enhance completeness.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources