Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DeepMap AI -- Earth Grounding

PYPI · DEEPMAP-EARTH-GROUNDING-MCP · 2 COMPONENTS · SCANNED SEP 21

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

+19 this week 64 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
Schema Quality & AI Usability56
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 624 tokens (~56/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 12% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.

pypi · deepmap-earth-grounding-mcp

# add to Claude Code
claude mcp add com-deepmapai-earth-grounding -- uvx deepmap-earth-grounding-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-deepmapai-earth-grounding": {
      "command": "uvx",
      "args": [
        "deepmap-earth-grounding-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-deepmapai-earth-grounding": {
      "command": "uvx",
      "args": [
        "deepmap-earth-grounding-mcp"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-deepmapai-earth-grounding --command uvx --arg deepmap-earth-grounding-mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-deepmapai-earth-grounding:
    command: "uvx"
    args: ["deepmap-earth-grounding-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-deepmapai-earth-grounding": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "deepmap-earth-grounding-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-deepmapai-earth-grounding -t stdio -c uvx -a deepmap-earth-grounding-mcp
// mcp.json
{
  "mcpServers": {
    "com-deepmapai-earth-grounding": {
      "command": "uvx",
      "args": [
        "deepmap-earth-grounding-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 +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.

  • 19 Sept 26 +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.

  • 17 Sept 26 +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.

  • 15 Sept 26 +16
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 13 Sept 26 +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.

  • 12 Sept 26 +1
    • Tool safety: pass → unverified security
    • Stability: 0.37 → unverified security
    • Schema quality: 40 → 56 functional
    • Tool coverage: 100 → unverified functional
    • Capabilities: fail → unverified functional
    • Tool coverage: 0% → 12% functional
    • First check of Schema quality: unverified functional
    • Package version: 0.1.0 → 0.3.0 functional
  • 11 Sept 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed pypi/deepmap-earth-grounding-mcp@0.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~624 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
capabilities ~20

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_hypothesis ~112

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.

NameTypeReqDescription
claimstringyesthe hypothesis in plain words, e.g. 'does dv/v predict earthquakes'
domainstringoptional filter, e.g. earthquake_precursor
limitinteger

No output schema declared.

No examples provided.

ground_stability ~46

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

NameTypeReqDescription
latnumberyes
lonnumberyes
radius_kmnumber

No output schema declared.

No examples provided.

ground_truth ~32

The bundled five-question answer + one provenance record.

NameTypeReqDescription
latnumberyes
lonnumberyes

No output schema declared.

No examples provided.

list_nulls ~66

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.

NameTypeReqDescription
domainstring
limitinteger

No output schema declared.

No examples provided.

resource_indication ~46

Geothermal / mineral / gas / water indication (gated, low-confidence).

NameTypeReqDescription
latnumberyes
lonnumberyes
typestring

No output schema declared.

No examples provided.

run_controlled_test ~121

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.

NameTypeReqDescription
latnumber
lonnumber
observablestringe.g. 'geomagnetic' (live) or 'synthetic' (demo)

No output schema declared.

No examples provided.

seismic_hazard ~51

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

NameTypeReqDescription
horizon_daysinteger
latnumberyes
lonnumberyes
regionstring

No output schema declared.

No examples provided.

space_weather_grid_risk ~42

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

NameTypeReqDescription
latnumberyes
lonnumberyes

No output schema declared.

No examples provided.

verify ~29

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

NameTypeReqDescription
claim_hashstring

No output schema declared.

No examples provided.

water_availability ~59

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

NameTypeReqDescription
depth_mnumber
latnumberyes
lonnumberyes

No output schema declared.

No examples provided.

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.