DaedalMap Earthquake Data
REMOTE · APP.DAEDALMAP.COM · SCANNED SEP 20
Global earthquake events from the USGS, 2150 BC-present: magnitude, depth, location, counts.
Available components
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 Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1200 tokens (~85/item across 14 items; 8 tools + 6 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the DaedalMap Earthquake Data MCP server?
DaedalMap Earthquake Data is a hosted endpoint at https://app.daedalmap.com/mcp/earthquakes, 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 · app.daedalmap.com
claude mcp add --transport http com-daedalmap-earthquakes 'https://app.daedalmap.com/mcp/earthquakes'
{
"mcpServers": {
"com-daedalmap-earthquakes": {
"url": "https://app.daedalmap.com/mcp/earthquakes"
}
}
} {
"servers": {
"com-daedalmap-earthquakes": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/earthquakes"
}
}
} [mcp_servers.com-daedalmap-earthquakes] url = "https://app.daedalmap.com/mcp/earthquakes"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-daedalmap-earthquakes": {
"type": "remote",
"url": "https://app.daedalmap.com/mcp/earthquakes",
"enabled": true
}
}
} openclaw mcp add com-daedalmap-earthquakes --url 'https://app.daedalmap.com/mcp/earthquakes' --transport streamable-http
mcp_servers:
com-daedalmap-earthquakes:
url: "https://app.daedalmap.com/mcp/earthquakes" {
"McpServers": {
"com-daedalmap-earthquakes": {
"Transport": "http",
"Url": "https://app.daedalmap.com/mcp/earthquakes"
}
}
} assistant mcp add com-daedalmap-earthquakes -t streamable-http -u 'https://app.daedalmap.com/mcp/earthquakes'
{
"mcpServers": {
"com-daedalmap-earthquakes": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/earthquakes"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 0
- “get_pack” added an optional parameter “detail” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 14 Sept 26 +7
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_catalog” rewrote its description, which is the text the model reads security
- Tool “get_disaster_link_chain” rewrote its description, which is the text the model reads security
- Tool “get_disaster_links_for_event” rewrote its description, which is the text the model reads security
- Tool “get_earthquake_events” rewrote its description, which is the text the model reads security
- Tool “get_live_earthquake_events” rewrote its description, which is the text the model reads security
- Tool “get_pack” rewrote its description, which is the text the model reads security
- Tool “get_tool_help” rewrote its description, which is the text the model reads security
- Tool “search_disaster_links” rewrote its description, which is the text the model reads security
- Resource “DaedalMap Earthquake Data Pack” was removed ▼ functional
- Schema quality: 101 → 83 ▲ functional
- Tool “get_catalog” now declares an output schema ▲ functional
- Tool “get_disaster_link_chain” now declares an output schema ▲ functional
- Tool “get_disaster_links_for_event” now declares an output schema ▲ functional
- Tool “get_earthquake_events” now declares an output schema ▲ functional
- Tool “get_live_earthquake_events” now declares an output schema ▲ functional
- Tool “get_pack” now declares an output schema ▲ functional
- Tool “get_tool_help” now declares an output schema ▲ functional
- Tool “search_disaster_links” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- New resource “Earthquakes Pack” functional
- 1 Sept 26 +58
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 31 Aug 26 −58
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Aug 26 0
- Tool “get_tool_help” rewrote its description, which is the text the model reads security
- Server version: 0.3.0 → 0.4.0 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 20 Sept 2026 · Probed https://app.daedalmap.com/mcp/earthquakes
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.daedalmap.com | CN=YR2,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | RSA 2048 | SHA256-RSA | 51023d45112daf6159a4fae4a177632589f |
| SANs: app.daedalmap.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.daedalmap.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| daedalmap.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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.daedalmap.com/mcp/earthquakes | Verified | 200 | |
| http (plaintext) | http://app.daedalmap.com/mcp/earthquakes | HTTPS enforced | 301 | https://app.daedalmap.com/mcp/earthquakes |
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 →
get_catalog Get Catalog ~33
List the current catalog-published data packs and their access lanes. Start here, then call get_pack for one selected pack.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_version | string | – | – |
| clarification | object | – | – |
| error | object | – | – |
| generated_at | string|null | – | – |
| guidance | object | – | – |
| next_step | object | – | – |
| pack_count | integer | – | – |
| packs | array | – | – |
| provenance | object | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| tool_families | array | – | – |
| warnings | array | – | – |
No examples provided.
get_disaster_link_chain Get Disaster Link Chain ~165
Expand one exact event ID into a bounded published cross-hazard chain. Use a canonical event row to obtain the ID first.
| Name | Type | Req | Description |
|---|---|---|---|
| cross_type_only | boolean | – | When true, only return cross-hazard links. Default true. |
| depth | integer | – | Maximum link-chain depth to traverse. Default 1. |
| event_id | string | yes | Exact disaster event id from a supported pack row, such as 'NOAA-SIG-2' or 'USA-CA-FIRE-215'. |
| pack_id | string | – | Optional pack id hint when the event id is ambiguous. Supported exact-event link packs are earthquakes, tsunamis, volcanoes, and wildfires. |
| request_id | string | – | Optional caller-supplied request id for tracing. |
| Name | Type | Req | Description |
|---|---|---|---|
| chains | array | – | – |
| clarification | object | – | – |
| count | integer | – | – |
| depth | integer | – | – |
| error | object | – | – |
| event_id | string | – | – |
| guidance | object | – | – |
| links | array | – | – |
| next_step | object | – | – |
| provenance | object | – | – |
| query_event_id | string | – | – |
| reason | string | – | – |
| related | array | – | – |
| request_id | string|null | – | – |
| resolved_event | object | – | – |
| warnings | array | – | – |
No examples provided.
get_disaster_links_for_event Get Disaster Links For Event ~147
Return published cross-hazard links for one exact event ID. Use a canonical event row to obtain the ID first.
| Name | Type | Req | Description |
|---|---|---|---|
| cross_type_only | boolean | – | When true, only return cross-hazard links. Default true. |
| event_id | string | yes | Exact disaster event id from a supported pack row, such as 'NOAA-SIG-2' or 'USA-CA-FIRE-215'. |
| pack_id | string | – | Optional pack id hint when the event id is ambiguous. Supported exact-event link packs are earthquakes, tsunamis, volcanoes, and wildfires. |
| request_id | string | – | Optional caller-supplied request id for tracing. |
| Name | Type | Req | Description |
|---|---|---|---|
| chains | array | – | – |
| clarification | object | – | – |
| count | integer | – | – |
| depth | integer | – | – |
| error | object | – | – |
| event_id | string | – | – |
| guidance | object | – | – |
| links | array | – | – |
| next_step | object | – | – |
| provenance | object | – | – |
| query_event_id | string | – | – |
| reason | string | – | – |
| related | array | – | – |
| request_id | string|null | – | – |
| resolved_event | object | – | – |
| warnings | array | – | – |
No examples provided.
get_earthquake_events Get Earthquake Events ~163
Query canonical earthquake history with structured metrics, filters, sorting, and a row limit. Use get_live_earthquake_events only for preliminary upstream data.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | yes | Structured filters including time ranges, region_ids, and compare clauses. |
| limit | integer | – | Maximum number of rows to return. For top-N requests, include a narrow time range or region_ids before sorting. |
| metrics | array | yes | Metric ids to return, such as 'event_count' or event attributes like 'magnitude'. |
| output | object | – | Optional output controls such as response format hints. |
| request_id | string | – | Optional caller-supplied request id for tracing and idempotency. |
| sort | – | – | Optional sort instructions for row-returning queries. |
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | – | – |
| clarification | object | – | – |
| error | object | – | – |
| filters_applied | object | – | – |
| guidance | object | – | – |
| limit | integer | – | – |
| next_step | object | – | – |
| pack_id | string | – | – |
| provenance | object | – | – |
| query_mode | string | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| row_count | integer | – | – |
| rows | array | – | – |
| sort | array | – | – |
| source_id | string | – | – |
| truncated | boolean | – | – |
| warnings | array | – | – |
No examples provided.
get_live_earthquake_events Get Live Earthquake Events ~211
Fetch recent preliminary USGS earthquake events in the shared data-result shape. Use get_earthquake_events for canonical enriched history.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | – | Optional exclusive-ish ISO-8601 end datetime. Defaults to now. |
| hours | integer | – | Recent lookback window in hours. Ignored when start_time is provided. |
| limit | integer | – | Maximum live rows to return. |
| max_latitude | number | – | Optional bounding box maximum latitude. |
| max_longitude | number | – | Optional bounding box maximum longitude. |
| min_latitude | number | – | Optional bounding box minimum latitude. |
| min_longitude | number | – | Optional bounding box minimum longitude. |
| min_magnitude | number | – | Minimum earthquake magnitude. Defaults to 2.5. |
| orderby | string | – | USGS result ordering. |
| request_id | string | – | Optional caller-supplied request id for tracing. |
| start_time | string | – | Optional inclusive ISO-8601 start datetime. |
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | – | – |
| clarification | object | – | – |
| error | object | – | – |
| filters_applied | object | – | – |
| guidance | object | – | – |
| limit | integer | – | – |
| next_step | object | – | – |
| pack_id | string | – | – |
| provenance | object | – | – |
| query_mode | string | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| row_count | integer | – | – |
| rows | array | – | – |
| sort | array | – | – |
| source_id | string | – | – |
| truncated | boolean | – | – |
| warnings | array | – | – |
No examples provided.
get_pack Get Pack ~90
Describe one catalog-published pack, including sources, metrics, coverage, freshness, access, and a first query. Call this before querying an unfamiliar pack.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Use lite for normal discovery. Use full only for one selected pack when its complete public metadata is required. |
| pack_id | string | yes | Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change. |
| Name | Type | Req | Description |
|---|---|---|---|
| clarification | object | – | – |
| error | object | – | – |
| guidance | object | – | – |
| material_policy | object | – | – |
| next_step | object | – | – |
| pack_id | string | – | – |
| provenance | object | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| sources | array | – | – |
| warnings | array | – | – |
No examples provided.
get_tool_help Get Tool Help ~51
Describe one tool visible on this facade, including its input contract, access limits, refusals, example, outputs, and recommended next calls.
| Name | Type | Req | Description |
|---|---|---|---|
| tool_name | string | yes | Exact tool name from tools/list. |
| Name | Type | Req | Description |
|---|---|---|---|
| access | object | – | – |
| clarification | object | – | – |
| error | object | – | – |
| examples | array | – | – |
| guidance | object | – | – |
| important_output_fields | array | – | – |
| input_schema | object | – | – |
| next_step | object | – | – |
| ok | boolean | – | – |
| provenance | object | – | – |
| purpose | string | – | – |
| reason | string | – | – |
| recommended_next_calls | array | – | – |
| request_id | string|null | – | – |
| title | string|null | – | – |
| tool_name | string | – | – |
| warnings | array | – | – |
No examples provided.
search_disaster_links Search Disaster Links ~160
Find published cross-hazard relationship families by event type and optional year range before choosing an exact event.
| Name | Type | Req | Description |
|---|---|---|---|
| end_event_type | string | – | Optional ending event type such as tsunami, flood, tornado, or earthquake. |
| limit | integer | – | Maximum number of matching chains to return. Default 10. |
| request_id | string | – | Optional caller-supplied request id for tracing. |
| start_event_type | string | – | Optional starting event type such as earthquake, hurricane, volcano, wildfire, flood, tornado, or tsunami. |
| via_event_type | string | – | Optional intermediate event type for bounded chain discovery. |
| year_end | integer | – | Optional inclusive ending year filter. |
| year_start | integer | – | Optional inclusive starting year filter. |
| Name | Type | Req | Description |
|---|---|---|---|
| chains | array | – | – |
| clarification | object | – | – |
| count | integer | – | – |
| depth | integer | – | – |
| error | object | – | – |
| event_id | string | – | – |
| guidance | object | – | – |
| links | array | – | – |
| next_step | object | – | – |
| provenance | object | – | – |
| query_event_id | string | – | – |
| reason | string | – | – |
| related | array | – | – |
| request_id | string|null | – | – |
| resolved_event | object | – | – |
| warnings | array | – | – |
No examples provided.
What is the DaedalMap Earthquake Data MCP server?
DaedalMap Earthquake Data is an MCP server listed in the public MCP registry as com.daedalmap/earthquakes. Global earthquake events from the USGS, 2150 BC-present: magnitude, depth, location, counts. This page covers its hosted endpoint (https://app.daedalmap.com/mcp/earthquakes).
Is the DaedalMap Earthquake Data MCP server safe to use?
DaedalMap Earthquake Data scores 88 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 DaedalMap Earthquake Data MCP server expose?
DaedalMap Earthquake Data exposes 8 tools: get_tool_help, get_catalog, get_pack, get_disaster_links_for_event, get_disaster_link_chain, and 3 more. Their descriptions and schemas cost roughly 1,020 tokens of context every time the server is loaded.
Does the DaedalMap Earthquake Data MCP server require authentication?
No. We connected to DaedalMap Earthquake Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DaedalMap Earthquake Data MCP server still maintained?
DaedalMap Earthquake Data is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.