A
licenseNot graded
qualityB
maintenanceEnables AI agents to query live earthquake and disaster event data, and to compute deterministic risk assessments with tamper-evident seals.
MIT
Earth Grounding MCP
by DeepMapAI
Related Servers
Alternatives to Earth Grounding MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to query cryptographically verified facts with zero-knowledge proofs, selective disclosure, and tamper-evident provenance.264 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables agents to query live NOAA/USGS space-weather and earthquake feeds, compute deterministic storm-risk assessments with hash-chained integrity seals, and verify data authenticity via JSON-RPC tools.MIT
- AlicenseNot gradedqualityBmaintenanceProvides sourced, current physical and environmental field-truth (weather, air quality, water, terrain, etc.) for any location, with provenance and typed silence to prevent hallucination.32 npm1Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to access verifiable DePIN supply-side telemetry, browse and purchase data products using credits, query datasets, and verify data provenance with cryptographic and zero-knowledge tools.10205 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to query Earth observation data, satellite imagery, active fires, and weather via natural language, returning interactive maps and briefs.12MIT
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