# DeepMap AI -- Earth Grounding (pypi · deepmap-earth-grounding-mcp)

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

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

## Components

- remote · `deepmapai.com`: 78/100, [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 (this document), [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

- Registry: `pypi`
- Package: `deepmap-earth-grounding-mcp`
- Version: `0.3.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (Proprietary) isn't a recognized OSI-approved license.
  - Actively maintained (last published 8 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 624 tokens (~56/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**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 12% 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**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

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

DeepMap AI -- Earth Grounding runs locally as a PyPI package, launched with uvx deepmap-earth-grounding-mcp. 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 com-deepmapai-earth-grounding -- uvx deepmap-earth-grounding-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-deepmapai-earth-grounding": {
      "command": "uvx",
      "args": [
        "deepmap-earth-grounding-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-deepmapai-earth-grounding": {
      "command": "uvx",
      "args": [
        "deepmap-earth-grounding-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-deepmapai-earth-grounding -- uvx deepmap-earth-grounding-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-deepmapai-earth-grounding": {
      "type": "local",
      "command": [
        "uvx",
        "deepmap-earth-grounding-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-deepmapai-earth-grounding --command uvx --arg deepmap-earth-grounding-mcp
```

### Hermes

```yaml
mcp_servers:
  com-deepmapai-earth-grounding:
    command: "uvx"
    args: ["deepmap-earth-grounding-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-deepmapai-earth-grounding": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "deepmap-earth-grounding-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-deepmapai-earth-grounding -t stdio -c uvx -a deepmap-earth-grounding-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-deepmapai-earth-grounding": {
      "command": "uvx",
      "args": [
        "deepmap-earth-grounding-mcp"
      ]
    }
  }
}
```

## 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 64, +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 63, +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 62, +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 61, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 45, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 60, +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 59, +1)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.37 → unverified
- [functional regression] Schema quality: 40 → 56
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: fail → unverified
- [functional improvement] Tool coverage: 0% → 12%
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.0 → 0.3.0

### 2026-09-11 (score 58, +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.

## MCP tools (11)

### `water_availability` (~59 tokens)

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

Input parameters:

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

### `seismic_hazard` (~51 tokens)

Seismic hazard via the public, outcome-excluded prediction ledger.

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, low-confidence).

Input parameters:

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

### `space_weather_grid_risk` (~42 tokens)

Live geomagnetic activity (Kp) as GIC / space-weather grid exposure.

Input parameters:

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

### `verify` (~29 tokens)

Verify a claim hash / the ledger hash chain against the Bitcoin anchor.

Input parameters:

- `claim_hash` (string)

### `ground_truth` (~32 tokens)

The bundled five-question answer + one provenance record.

Input parameters:

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

### `capabilities` (~20 tokens)

What DeepMap can answer now + coverage counts (public aggregate).

### `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` (~121 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). Free tier runs a synthetic demo; the live lab is the authenticated tier.

Input parameters:

- `lat` (number)
- `lon` (number)
- `observable` (string): e.g. 'geomagnetic' (live) or 'synthetic' (demo)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-deepmapai-earth-grounding/deepmap-earth-grounding-mcp#diagnostics

## Score history

- 2026-09-21: 64
- 2026-09-20: 63
- 2026-09-19: 63
- 2026-09-18: 62
- 2026-09-17: 62
- 2026-09-16: 61
- 2026-09-15: 61
- 2026-09-14: 45
- 2026-09-13: 60
- 2026-09-12: 59
- 2026-09-11: 58
- 2026-09-10: 57
- 2026-09-09: 57
- 2026-09-08: 56
- 2026-09-07: 53
- 2026-09-06: 53
- 2026-09-05: 53
- 2026-09-04: 53
- 2026-09-03: 53
- 2026-09-02: 53
- 2026-09-01: 53
- 2026-08-31: 53

## 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 PyPI package (deepmap-earth-grounding-mcp).

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

DeepMap AI -- Earth Grounding scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 624 tokens of context every time the server is loaded.

### 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.

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

DeepMap AI -- Earth Grounding declares the Proprietary licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/deepmap-earth-grounding-mcp/
- Socket report: https://socket.dev/pypi/package/deepmap-earth-grounding-mcp
- Website: https://deepmapai.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-deepmapai-earth-grounding/deepmap-earth-grounding-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-deepmapai-earth-grounding/deepmap-earth-grounding-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-deepmapai-earth-grounding/deepmap-earth-grounding-mcp