Skip to main content
Glama
DeepMapAI

Earth Grounding MCP

by DeepMapAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Earth Grounding MCP

No user-submitted related servers found.

    Related Servers

    • pointmoon-mcp

      johangace
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides sourced, current physical and environmental field-truth (weather, air quality, water, terrain, etc.) for any location, with provenance and typed silence to prevent hallucination.
      20 npm
      Apache 2.0

    • APEX PSI MCP Server

      kawal393
      A
      license
      A
      quality
      C
      maintenance
      Provides cryptographic truth infrastructure for AI agents, enabling them to seal content with SHA-256 and Ed25519, verify receipts, anchor them to Bitcoin via OpenTimestamps, generate citations, and audit chains of receipts.
      5
      24 npm
      1
      MIT
    • dynamicfeed-mcp by Fluxdyne

      dynamicfeed-mcpofficial

      Fluxdyne
      A
      license
      Not graded
      quality
      C
      maintenance
      62 live, cryptographically signed data tools for AI agents and robots: weather, natural hazards, flights, shipping, space, CVEs, sanctions, software versions, sea ice and more. Every datapoint carries source, licence, timestamp and an Ed25519 signature.
      9 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

    B3/5.0

    Scored across 11 tools

    Disambiguation4/5

    The hazard tools (water_availability, seismic_hazard, ground_stability, space_weather_grid_risk) each target a distinct exposure with clear boundaries. However, resource_indication explicitly covers 'water' and overlaps with water_availability, which could cause misselection, and the meta tools (ground_truth, capabilities, check_hypothesis) require careful reading to distinguish 'answer now' vs 'registry query'.

    Naming Consistency4/5

    All names use snake_case, which is consistent. There is a minor stylistic split between bare domain nouns (seismic_hazard, ground_stability, capabilities) and verb_noun action names (check_hypothesis, list_nulls, run_controlled_test, verify), but each name is readable and predictable.

    Tool Count5/5

    11 tools is well within the sweet spot for a domain server and each tool appears to earn its place across hazard lookups, verification, and the hypothesis/null registry.

    Completeness4/5

    The surface covers a broad lifecycle: query geohazard data, verify provenance/anchors, test hypotheses, list nulls, and run controlled tests. There is no obvious create/update flow, but for a read-oriented ground-truth service this is close to complete; minor gaps are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources