DeepMap AI -- Earth Grounding
REMOTE · DEEPMAPAI.COM · 2 COMPONENTS
Verifiable Earth ground truth for AI agents: water, hazard, ground stability, resource, with proof.
Available components
Last scanned (14 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 728 tokens (~66/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 Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% 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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 23 Oct 26 −1
- Tool “capabilities” rewrote its description, which is the text the model reads security
- Tool “list_nulls” rewrote its description, which is the text the model reads security
- Tool “run_controlled_test” rewrote its description, which is the text the model reads security
- 21 Oct 26 0
- Tool “resource_indication” rewrote its description, which is the text the model reads security
- Tool “water_availability” rewrote its description, which is the text the model reads security
- 30 Sept 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Sept 26 0
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2024-11-05 → 2026-07-28 functional
- 2 Sept 26 0
- Schema quality: 45 → 67 ▼ functional
- Tool coverage: 0% → 17% ▲ functional
- Server version: 0.1.0 → 0.3.0 functional
- New tool “run_controlled_test” functional
- New tool “check_hypothesis” functional
- New tool “list_nulls” functional
- 1 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 · Probed https://deepmapai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=deepmapai.com | CN=YE1,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6c007de6c47d172d53e9e0f94ab6d79baad |
| SANs: deepmapai.com, www.deepmapai.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of deepmapai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| deepmapai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://deepmapai.com/mcp | Verified | 200 | |
| http (plaintext) | http://deepmapai.com/mcp | HTTPS enforced | 301 | https://deepmapai.com/mcp |
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 ~30
What DeepMap AI can answer now + coverage counts (public aggregate; tracks the library, leaks no proprietary data).
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 ~44
The bundled five-question answer (water / stability / hazard / resource / provability) + one provenance record.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
No output schema declared.
No examples provided.
list_nulls ~67
List DeepMap AI'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 ~44
Geothermal / mineral / water indication (gated, honest null).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
run_controlled_test ~207
The Lab-as-an-API: run a REAL, bounded controlled test at a location and get an honest verdict. DeepMap AI 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
seismic_hazard ~57
Seismic hazard via the public, outcome-excluded prediction ledger (no platform-wide accuracy figure).
| 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 ~37
GIC / space-weather exposure for infrastructure at a point.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
No output schema declared.
No examples provided.
verify ~31
Verify a claim / the ledger hash chain against the Bitcoin-anchored record.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_hash | string | – | – |
No output schema declared.
No examples provided.
water_availability ~53
Water availability at a point. Free tier = public GRACE groundwater trend.
| Name | Type | Req | Description |
|---|---|---|---|
| authenticated | boolean | – | – |
| 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 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.
remote · deepmapai.com
claude mcp add --transport http com-deepmapai-earth-grounding 'https://deepmapai.com/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 hosted endpoint (https://deepmapai.com/mcp).
Is the DeepMap AI -- Earth Grounding MCP server safe to use?
DeepMap AI -- Earth Grounding scores 81 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 728 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.