Earth Grounding MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPMAP_API_KEY | Yes | Your DeepMap API key. A free demo key 'demo-free' works with no signup. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| water_availabilityB | Replenishable-water availability at a point. Free = public groundwater trend; paid adds a derived (non-locating) atlas indication. |
| seismic_hazardD | Seismic hazard via the public, outcome-excluded prediction ledger. |
| ground_stabilityC | Subsidence / void / karst / fault risk from verified observations. |
| resource_indicationC | Geothermal / mineral / gas / water indication (gated, low-confidence). |
| space_weather_grid_riskC | Live geomagnetic activity (Kp) as GIC / space-weather grid exposure. |
| verifyC | Verify a claim hash / the ledger hash chain against the Bitcoin anchor. |
| ground_truthC | The bundled five-question answer + one provenance record. |
| capabilitiesB | What DeepMap can answer now + coverage counts (public aggregate). |
| check_hypothesisB | Has this Earth-science hypothesis been tested? Query the Null Museum + the Bitcoin-anchored hypothesis registry. A direct match returns the verdict + the positive control that proves the test was sensitive + the honest bound + the anchor -- so an agent never re-runs a dead idea. |
| list_nullsC | List DeepMap's documented nulls / bounds / retractions (the Null Museum), optionally by domain -- each with the positive control that makes it trustworthy. We carry our own retractions; that is the credibility. |
| run_controlled_testA | The Lab-as-an-API: run a REAL, bounded controlled test at a location and get an honest verdict. DeepMap fetches real data, runs a lock-in detection with a local-background null AND a positive control (a known reference line must be recovered, else UNTESTABLE). Free tier runs a synthetic demo; the live lab is the authenticated tier. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
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'.
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.
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.
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.