# DaedalMap Earthquake Data (remote · app.daedalmap.com)

Global earthquake events from the USGS, 2150 BC-present: magnitude, depth, location, counts.

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

## Components

- remote · `app.daedalmap.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-daedalmap-earthquakes/mcp-earthquakes-2.md), [page](https://verifymcp.io/servers/com-daedalmap-earthquakes/mcp-earthquakes-2)

## Channel facts

- Endpoint: `https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1058 tokens (~96/item across 11 items; 5 tools + 6 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the DaedalMap Earthquake Data MCP server?

DaedalMap Earthquake Data is a hosted endpoint at https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry, 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.

### Claude

```bash
claude mcp add --transport http com-daedalmap-earthquakes 'https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry'
```

### Cursor

```json
{
  "mcpServers": {
    "com-daedalmap-earthquakes": {
      "url": "https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-daedalmap-earthquakes": {
      "type": "http",
      "url": "https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-daedalmap-earthquakes]
url = "https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-daedalmap-earthquakes": {
      "type": "remote",
      "url": "https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-daedalmap-earthquakes --url 'https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-daedalmap-earthquakes:
    url: "https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry"
```

### Netclaw

```json
{
  "McpServers": {
    "com-daedalmap-earthquakes": {
      "Transport": "http",
      "Url": "https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-daedalmap-earthquakes -t streamable-http -u 'https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry'
```

### Other

```json
{
  "mcpServers": {
    "com-daedalmap-earthquakes": {
      "type": "http",
      "url": "https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-20 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 78, +2)

- [functional improvement] MCP protocol: fail → pass
- [functional] MCP protocol version: 2025-06-18 → 2026-07-28

### 2026-11-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 75, +1)

- [security] Tool “get_pack” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 79 → 96
- [cosmetic] “get_pack” added an optional parameter “metrics”
- [cosmetic] “get_pack” added an optional parameter “search”
- [cosmetic] “get_pack” added an optional parameter “source_id”

### 2026-11-13 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 74)

First indexed and scored.

## MCP tools (5)

### `get_tool_help` (~84 tokens)

Get Tool Help

Describe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.

Input parameters:

- `question` (string): Optional question used only with a topic overview.
- `tool_name` (string): Exact tool name from tools/list. Do not combine with topic.
- `topic` (string): Workflow overview. Do not combine with tool_name.

Output parameters:

- `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)

### `get_catalog` (~125 tokens)

List Published Packs or Geographies

Choose data or geometry to list published pack IDs or family and scope IDs. The response includes a complete catalog download URL. Use get_pack for data or get_geography for geometry. Current catalog: The same geography tools work worldwide across a cataloged baseline of 252 geographic entities, reaching up to Admin 2. Where additional country releases are available, the same calls automatically return deeper administrative tiers or maintained reference families. Additional detail is currently available for Australia, Brazil, Canada, France, Germany, Mexico, United Kingdom, United States.

Input parameters:

- `catalog` (string, required): Required directory selector.

Output parameters:

- `catalog` (string)
- `catalog_version` (string)
- `clarification` (object)
- `detail` (string)
- `download_url` (string)
- `error` (object)
- `excluded_count` (integer)
- `families` (array)
- `free_get_data_policy_note` (string)
- `generated_at` (string|null)
- `guidance` (object)
- `next_step` (object)
- `pack_count` (integer)
- `packs` (array)
- `provenance` (object)
- `reason` (string)
- `request_id` (string|null)
- `resolved_query` (object)
- `result_status` (string)
- `scopes` (array)
- `tool_families` (array)
- `uncertain_count` (integer)
- `uncertain_packs` (array)
- `warnings` (array)

### `get_pack` (~241 tokens)

Inspect One Data Pack

Narrow one data pack before get_data. With only pack_id, lists the pack's sources and their coverage. Add source_id to list that source's metrics (name, unit, years, aggregation) and its filterable and sortable fields; search to match metrics across the pack by name, description, or keyword; or metrics for full detail on up to 10 exact ids.

Input parameters:

- `metrics` (array): Optional. Up to 10 exact metric ids from this pack. Returns full stored detail for each, including description, coverage by era, value statistics, and every source that holds it.
- `pack_id` (string, required): Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
- `search` (string): Optional. Terms matched against metric ids, names, descriptions, and keywords across this pack's sources; every term must match. Returns up to 25 compact metric lines.
- `source_id` (string): Optional. One source_id from this pack's sources list. Returns every metric in that source with name, unit, years, and aggregation, plus the source's filterable fields, sortable fields, and time fiel…

Output parameters:

- `catalog` (string)
- `clarification` (object)
- `detail` (string)
- `download_call` (object)
- `download_url` (string)
- `error` (object)
- `full_call` (object)
- `guidance` (object)
- `match_count` (integer)
- `material_policy` (object)
- `metrics` (array)
- `next_step` (object)
- `pack_id` (string)
- `provenance` (object)
- `query_contract` (object)
- `reason` (string)
- `request_id` (string|null)
- `source` (object)
- `sources` (array)
- `truncated` (boolean)
- `unknown_metrics` (array)
- `warnings` (array)

### `get_event` (~215 tokens)

Get Event

Retrieve one exact disaster event and explicitly requested relationships, affected places, native observations, or geometry. Use get_data to obtain the stable event_id first.

Input parameters:

- `event_id` (string, required): Exact stable event_id returned by a disaster-pack get_data row.
- `geometry_mode` (string): current returns the representative/current shape; timeline returns bounded progression frames where supported.
- `include` (array): Optional companion layers. Omit for the lightweight event summary. Geometry is never returned implicitly.
- `limit` (integer): Per-section ceiling for relationships, affected places, observations, or geometry frames.
- `pack_id` (string, required): Required disaster pack_id that returned this event_id from get_data. The tool never searches other packs.
- `relationship_depth` (integer): Bounded cross-hazard traversal depth when relationships is included.
- `request_id` (string): Optional caller-supplied request id for tracing.
- `source_id` (string, required): Required source_id from the same get_data result. Must identify one published event source in pack_id.

Output parameters:

- `affected_places` (object)
- `available` (object)
- `clarification` (object)
- `error` (object)
- `event` (object)
- `event_id` (string)
- `event_type` (string)
- `geometry` (object)
- `guidance` (object)
- `included` (array)
- `next_step` (object)
- `next_steps` (object)
- `observations` (object)
- `pack_id` (string)
- `provenance` (object)
- `reason` (string)
- `relationships` (object)
- `request_id` (string|null)
- `schema_class` (string)
- `source_id` (string)
- `warnings` (array)

### `get_data` (~213 tokens)

Get Data

Retrieve rows from one selected published data pack using exact metrics, loc_id-based region filters, time/metric filters, sorting, and a row limit. Disaster event rows include stable event_id values for get_event drill-down. A parent administrative loc_id selects matching descendant rows at the pack's published grain. Call get_pack first; geometry families use their focused next-step tools.

Input parameters:

- `filters` (object, required)
- `limit` (integer): Maximum number of rows to return for the requested source or pack.
- `metrics` (array, required): Exact metric ids from get_pack. Use event_count for aggregate counts only when get_pack publishes it.
- `output` (object): Optional response controls. v1 supports rows only.
- `pack_id` (string, required): Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
- `request_id` (string): Optional caller-supplied request id for tracing and idempotency.
- `sort`: Sort by a sortable field from get_pack; direction defaults to asc.

Output parameters:

- `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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-daedalmap-earthquakes/mcp-earthquakes-2#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 79
- 2026-11-19: 78
- 2026-11-18: 76
- 2026-11-17: 76
- 2026-11-16: 75
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 74
- 2026-11-12: 74

## Common questions

### 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?registry=mcpregistry).

### Is the DaedalMap Earthquake Data MCP server safe to use?

DaedalMap Earthquake Data scores 79 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 5 tools: get_tool_help, get_catalog, get_pack, get_event, get_data. Their descriptions and schemas cost roughly 878 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the DaedalMap Earthquake Data MCP server?

VerifyMCP ran 13 checks on DaedalMap Earthquake Data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://app.daedalmap.com/mcp/earthquakes?registry=mcpregistry
- Repository: https://github.com/xyver/daedal-map
- Website: https://www.daedalmap.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-daedalmap-earthquakes/mcp-earthquakes-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-daedalmap-earthquakes/mcp-earthquakes-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-daedalmap-earthquakes/mcp-earthquakes-2.json
- HTML version of this page: https://verifymcp.io/servers/com-daedalmap-earthquakes/mcp-earthquakes-2
