DeepMap AI -- Earth Grounding
PYPI · DEEPMAP-EARTH-GROUNDING-MCP · 2 COMPONENTS
Verifiable Earth ground truth for AI agents: water, hazard, ground stability, resource, with proof.
Available components
Last scanned (7 hours ago)
Scores higher than 66% of PyPI servers
Category Maps and Location
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 build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (Proprietary) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 53 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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 5 Nov 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 |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | 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 →
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | the hypothesis in plain words, e.g. 'does dv/v predict earthquakes' |
| domain | string | – | optional filter, e.g. earthquake_precursor |
| limit | integer | – | – |
No output schema declared.
No examples provided.
ground_stability ~46
Subsidence / void / karst / fault risk from verified observations.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
| radius_km | number | – | – |
No output schema declared.
No examples provided.
ground_truth ~32
The bundled five-question answer + one provenance record.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
resource_indication ~46
Geothermal / mineral / gas / water indication (gated, low-confidence).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
| type | string | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | – |
| lon | number | – | – |
| observable | string | – | e.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.
| Name | Type | Req | Description |
|---|---|---|---|
| horizon_days | integer | – | – |
| lat | number | yes | – |
| lon | number | yes | – |
| region | string | – | – |
No output schema declared.
No examples provided.
space_weather_grid_risk ~42
Live geomagnetic activity (Kp) as GIC / space-weather grid exposure.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
No output schema declared.
No examples provided.
verify ~29
Verify a claim hash / the ledger hash chain against the Bitcoin anchor.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_hash | string | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| depth_m | number | – | – |
| lat | number | yes | – |
| lon | number | yes | – |
No output schema declared.
No examples provided.
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
claude mcp add com-deepmapai-earth-grounding -- uvx deepmap-earth-grounding-mcp
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 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 5 November 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.
What did VerifyMCP test on the DeepMap AI -- Earth Grounding MCP server?
VerifyMCP ran 15 checks on DeepMap AI -- Earth Grounding, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about DeepMap AI -- Earth Grounding: Security disclosure. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.