# DeepMap AI -- Earth Grounding (remote · deepmapai.com)

Verifiable Earth ground truth for AI agents: water, hazard, ground stability, resource, with proof.

- Trust score: 78/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `deepmapai.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-deepmapai-earth-grounding/deepmapai.md), [page](https://verifymcp.io/servers/com-deepmapai-earth-grounding/deepmapai)
- pypi · `deepmap-earth-grounding-mcp`: 64/100, [markdown](https://verifymcp.io/servers/com-deepmapai-earth-grounding/deepmap-earth-grounding-mcp.md), [page](https://verifymcp.io/servers/com-deepmapai-earth-grounding/deepmap-earth-grounding-mcp)

## Channel facts

- Endpoint: `https://deepmapai.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 747 tokens (~67/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 72/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 17% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the DeepMap AI -- Earth Grounding MCP server?

DeepMap AI -- Earth Grounding is a hosted endpoint at https://deepmapai.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-deepmapai-earth-grounding 'https://deepmapai.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-deepmapai-earth-grounding": {
      "url": "https://deepmapai.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-deepmapai-earth-grounding": {
      "type": "http",
      "url": "https://deepmapai.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-deepmapai-earth-grounding]
url = "https://deepmapai.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-deepmapai-earth-grounding": {
      "type": "remote",
      "url": "https://deepmapai.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-deepmapai-earth-grounding --url 'https://deepmapai.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-deepmapai-earth-grounding:
    url: "https://deepmapai.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-deepmapai-earth-grounding": {
      "Transport": "http",
      "Url": "https://deepmapai.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-deepmapai-earth-grounding -t streamable-http -u 'https://deepmapai.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-deepmapai-earth-grounding": {
      "type": "http",
      "url": "https://deepmapai.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 73, +3)

- [functional improvement] MCP protocol: fail → pass
- [functional] MCP protocol version: 2024-11-05 → 2026-07-28

### 2026-09-11 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (11)

### `water_availability` (~73 tokens)

Replenishable-water availability at a point. Free tier = public GRACE groundwater trend; authenticated tier adds a derived (non-locating) replenishable-atlas indication.

Input parameters:

- `authenticated` (boolean)
- `depth_m` (number)
- `lat` (number, required)
- `lon` (number, required)

### `seismic_hazard` (~57 tokens)

Seismic hazard via the public, outcome-excluded prediction ledger (no platform-wide accuracy figure).

Input parameters:

- `horizon_days` (integer)
- `lat` (number, required)
- `lon` (number, required)
- `region` (string)

### `ground_stability` (~46 tokens)

Subsidence / void / karst / fault risk from verified observations.

Input parameters:

- `lat` (number, required)
- `lon` (number, required)
- `radius_km` (number)

### `resource_indication` (~46 tokens)

Geothermal / mineral / gas / water indication (gated, honest null).

Input parameters:

- `lat` (number, required)
- `lon` (number, required)
- `type` (string)

### `space_weather_grid_risk` (~37 tokens)

GIC / space-weather exposure for infrastructure at a point.

Input parameters:

- `lat` (number, required)
- `lon` (number, required)

### `verify` (~31 tokens)

Verify a claim / the ledger hash chain against the Bitcoin-anchored record.

Input parameters:

- `claim_hash` (string)

### `ground_truth` (~44 tokens)

The bundled five-question answer (water / stability / hazard / resource / provability) + one provenance record.

Input parameters:

- `lat` (number, required)
- `lon` (number, required)

### `capabilities` (~29 tokens)

What DeepMap can answer now + coverage counts (public aggregate; tracks the library, leaks no proprietary data).

### `check_hypothesis` (~112 tokens)

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.

Input parameters:

- `claim` (string, required): the hypothesis in plain words, e.g. 'does dv/v predict earthquakes'
- `domain` (string): optional filter, e.g. earthquake_precursor
- `limit` (integer)

### `list_nulls` (~66 tokens)

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.

Input parameters:

- `domain` (string)
- `limit` (integer)

### `run_controlled_test` (~206 tokens)

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) -- so an agent gets a grounded result it cannot fake. Free tier runs a synthetic demo; the live lab is the authenticated tier. v1 recipe: periodic-signal detection on the geomagnetic field.

Input parameters:

- `carrier` (string): a named line (M2, S1, S2, O1, K1, annual...) or a number in cycles/day
- `hypothesis` (string): optional -- the claim in plain words, for context
- `lat` (number)
- `lon` (number)
- `observable` (string): e.g. 'geomagnetic' (live) or 'synthetic' (demo)
- `window_days` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-deepmapai-earth-grounding/deepmapai#diagnostics

## Score history

- 2026-09-21: 78
- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 73
- 2026-09-11: 70
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 66
- 2026-09-03: 66
- 2026-09-02: 66
- 2026-09-01: 64
- 2026-08-31: 63

## Common questions

### What is the DeepMap AI -- Earth Grounding MCP server?

DeepMap AI -- Earth Grounding is an MCP server listed in the public MCP registry as com.deepmapai/earth-grounding. Verifiable Earth ground truth for AI agents: water, hazard, ground stability, resource, with proof. This page covers its hosted endpoint (https://deepmapai.com/mcp).

### Is the DeepMap AI -- Earth Grounding MCP server safe to use?

DeepMap AI -- Earth Grounding scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the DeepMap AI -- Earth Grounding MCP server expose?

DeepMap AI -- Earth Grounding exposes 11 tools: water_availability, seismic_hazard, ground_stability, resource_indication, space_weather_grid_risk, and 6 more. Their descriptions and schemas cost roughly 747 tokens of context every time the server is loaded.

### Does the DeepMap AI -- Earth Grounding MCP server require authentication?

No. We connected to DeepMap AI -- Earth Grounding without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DeepMap AI -- Earth Grounding MCP server still maintained?

DeepMap AI -- Earth Grounding is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://deepmapai.com/mcp
- Website: https://deepmapai.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-deepmapai-earth-grounding/deepmapai.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-deepmapai-earth-grounding/deepmapai.json
- HTML version of this page: https://verifymcp.io/servers/com-deepmapai-earth-grounding/deepmapai