Skip to main content
Glama
atlasfetch-dev

atlasfetch-mcp

Official
by atlasfetch-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to atlasfetch-mcp

No user-submitted related servers found.

    Related Servers

    • Location MCP Server

      v5tech
      A
      license
      A
      quality
      D
      maintenance
      Enables IP address location and latitude/longitude address queries, providing detailed geographic information such as country, province, city, and district.
      2
      10 npm
      MIT

    • mcp-geocodio

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables geocoding and reverse geocoding of addresses, including batch processing up to 10,000 addresses and optional data fields such as congressional district, census/FIPS, timezone, and demographics.
      12 npm
      MIT

    • mcp-opencages

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables forward and reverse geocoding using the OpenCage API, allowing conversion between addresses and coordinates.
      8 npm
      MIT

    • chuk-mcp-geocoder

      fastmcp-me
      A
      license
      A
      quality
      D
      maintenance
      Provides forward/reverse geocoding, bounding box extraction, nearby places discovery, batch geocoding, route waypoints, and administrative boundary lookup using OpenStreetMap data.
      10
      Apache 2.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.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: forward geocode (geocode_address) vs reverse geocode (lookup_location), routing (get_route), and boundary management (create/add/update/list). Descriptions explicitly cross-reference the correct alternative (e.g., 'For the other direction... use geocode_address'), leaving no ambiguity even between inverse geocoding tools.

    Naming Consistency5/5

    All tools follow a clean snake_case verb_noun pattern (lookup_location, geocode_address, get_route, add_boundary, create_boundary_set, list_boundary_sets, update_boundary). Multi-word nouns are handled consistently, and no mixed conventions appear.

    Tool Count5/5

    Seven tools is well-scoped for a geocoding/routing/boundary service: three geospatial query tools and four boundary-management tools. Each earns its place without feeling bloated or thin.

    Completeness3/5

    Forward/reverse geocoding and routing are covered, and boundary management has create/add/update/list, but there is no delete_boundary, delete_boundary_set, or get_boundary for a single record. Batch geocoding is also explicitly deferred to the raw API, leaving a notable lifecycle gap that will force workarounds.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources