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
      6 npm
      MIT

    • mcp-geocodio

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      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.
      MIT

    • mcp-opencages

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables forward and reverse geocoding using the OpenCage API, allowing conversion between addresses and coordinates.
      2 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 targets a distinct operation: listing sets, performing a lookup, creating a set, and adding a polygon. The boundary-set vs boundary distinction is clear from names and descriptions, so an agent is unlikely to select the wrong tool.

    Naming Consistency5/5

    All tool names follow a consistent lowercase verb_noun pattern: list_boundary_sets, lookup_location, create_boundary_set, add_boundary. There are no mixed casing or vague verb variations.

    Tool Count5/5

    Four tools is a well-scoped set for a focused geofencing/reverse-geocoding server. Each tool covers a necessary step in the core workflow without redundant additions.

    Completeness2/5

    The set is missing obvious lifecycle operations: boundaries and sets cannot be updated, deleted, or listed individually, and newly created sets cannot be activated or granted to API keys from this server, forcing a manual dashboard step. This leaves agents with a one-way create-and-add workflow and no way to correct mistakes or complete the queryability setup.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources