Skip to main content
Glama
CSOAI-ORG

Gods Eye Geospatial MCP

by CSOAI-ORG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Gods Eye Geospatial MCP

No user-submitted related servers found.

    Related Servers

    • geo-mcp-servers

      a1964378
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables geospatial operations such as geocoding, routing, map visualization, satellite imagery, and weather data through a unified MCP interface, making Earth data accessible to non-programmers.
      -

    • GeoSight MCP Server

      armaasinghn
      A
      license
      Not graded
      quality
      D
      maintenance
      Production-ready satellite imagery analysis server that enables natural language queries for Earth observation data, including land cover classification, vegetation monitoring, water detection, change detection, and automated environmental reporting.
      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
      16 npm
      MIT

    • geopera-mcp

      geo-pera
      A
      license
      C
      quality
      D
      maintenance
      MCP server for the Geopera geospatial data platform that enables AI agents to discover imagery, place and manage orders, and run analytics using the same API as other Geopera clients.
      100
      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

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: policy retrieval, provenance checking, data source listing, attestation signing, and query planning. No overlap in functionality.

    Naming Consistency2/5

    Naming patterns are inconsistent: 'care_membrane_policy' is a noun phrase, while 'check_data_provenance' and 'list_data_sources' follow verb_noun, but 'sign_data_provenance_attestation' is verbose, and 'situational_query' is adjective_noun. No consistent convention.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its focus on geospatial data provenance and situational awareness. Each tool adds distinct value without unnecessary bloat.

    Completeness4/5

    The tool set covers core workflows: listing sources, checking provenance, signing attestations, and planning queries. Minor gaps exist (e.g., no tool to fetch actual tile data, but that's a Pro feature), but for the stated purpose it is largely complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources