Skip to main content
Glama
atlasfetch-dev

atlasfetch-mcp

Official
by atlasfetch-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
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
      7 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.
      25 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.
      22 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 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: creating a set, adding a boundary to an existing set, listing sets, and performing a reverse geocode/boundary lookup. There is no overlap in action or resource, so an agent can select the right tool without ambiguity.

    Naming Consistency5/5

    All four tools follow a consistent snake_case verb_noun pattern: add_boundary, lookup_location, create_boundary_set, list_boundary_sets. The convention is predictable and readable throughout.

    Tool Count4/5

    Four tools is a reasonable count for a focused geocoding and boundary-upload service, and each tool earns its place. However, the set is a bit thin for boundary management, missing even basic inspection or cleanup operations.

    Completeness2/5

    The surface covers creating sets, adding boundaries, listing sets, and lookups, but there is no way to delete or update a boundary or set, nor to list the individual boundaries inside a set. These are significant gaps that will prevent agents from managing or cleaning up boundary data.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources