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.

DaedalMap Tsunami Data

REMOTE · APP.DAEDALMAP.COM · SCANNED SEP 21

Global tsunami events from NOAA NCEI, 2000 BC-present: wave height, runups, and counts.

0 this week 25 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the DaedalMap Tsunami Data MCP server?

DaedalMap Tsunami Data is a hosted endpoint at https://app.daedalmap.com/mcp/tsunamis, 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

# add to Claude Code
claude mcp add --transport http com-daedalmap-tsunamis 'https://app.daedalmap.com/mcp/tsunamis'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-daedalmap-tsunamis": {
      "url": "https://app.daedalmap.com/mcp/tsunamis"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-daedalmap-tsunamis": {
      "type": "http",
      "url": "https://app.daedalmap.com/mcp/tsunamis"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-daedalmap-tsunamis]
url = "https://app.daedalmap.com/mcp/tsunamis"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-daedalmap-tsunamis": {
      "type": "remote",
      "url": "https://app.daedalmap.com/mcp/tsunamis",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-daedalmap-tsunamis --url 'https://app.daedalmap.com/mcp/tsunamis' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-daedalmap-tsunamis:
    url: "https://app.daedalmap.com/mcp/tsunamis"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-daedalmap-tsunamis": {
      "Transport": "http",
      "Url": "https://app.daedalmap.com/mcp/tsunamis"
    }
  }
}
# add to Vellum
assistant mcp add com-daedalmap-tsunamis -t streamable-http -u 'https://app.daedalmap.com/mcp/tsunamis'
// mcp.json
{
  "mcpServers": {
    "com-daedalmap-tsunamis": {
      "type": "http",
      "url": "https://app.daedalmap.com/mcp/tsunamis"
    }
  }
}

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

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.

  • 14 Sept 26 −56
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: pass → unverified security
    • Tool safety: pass → unverified security
    • Transport: 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
  • 1 Sept 26 0
    • Stability: 0.97 → pass security
  • 31 Aug 26 0
    • Stability: pass → 0.97 functional
  • 26 Aug 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 Aug 26 +1
    • Stability: 0.97 → pass security
  • 24 Aug 26 +10
    • Transport: fail → pass security
  • 23 Aug 26 70
    • Transport: pass → fail security
  • 15 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
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 · Probed https://app.daedalmap.com/mcp/tsunamis

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 404
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/tsunamis HTTP error 404
http (plaintext) http://app.daedalmap.com/mcp/tsunamis HTTPS enforced 301 https://app.daedalmap.com/mcp/tsunamis
MCP tools · 7 exposed · ~1,006 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
get_catalog ~26

Free discovery. Returns the list of live agent-ready data packs available on DaedalMap.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_disaster_link_chain ~190

Free linked-disaster helper. Expands one exact disaster event id into a bounded related-event chain. Use this only when you already have an exact event id from a supported pack such as earthquakes, tsunamis, volcanoes, or wildfires.

NameTypeReqDescription
cross_type_onlybooleanWhen true, only return cross-hazard links. Default true.
depthintegerMaximum link-chain depth to traverse. Default 1.
event_idstringyesExact disaster event id from a supported pack row, such as 'NOAA-SIG-2' or 'USA-CA-FIRE-215'.
pack_idstringOptional pack id hint when the event id is ambiguous. Supported exact-event link packs are earthquakes, tsunamis, volcanoes, and wildfires.
request_idstringOptional caller-supplied request id for tracing.

No output schema declared.

No examples provided.

get_disaster_links_for_event ~175

Free linked-disaster helper. Resolves one exact disaster event id into its published related-disaster links. Use this only when you already have an exact event id from a supported pack such as earthquakes, tsunamis, volcanoes, or wildfires.

NameTypeReqDescription
cross_type_onlybooleanWhen true, only return cross-hazard links. Default true.
event_idstringyesExact disaster event id from a supported pack row, such as 'NOAA-SIG-2' or 'USA-CA-FIRE-215'.
pack_idstringOptional pack id hint when the event id is ambiguous. Supported exact-event link packs are earthquakes, tsunamis, volcanoes, and wildfires.
request_idstringOptional caller-supplied request id for tracing.

No output schema declared.

No examples provided.

get_pack ~80

Free discovery. Returns detailed metadata, coverage, freshness, preferred canonical tool guidance, and first-query examples for one pack. Call this before querying a new pack so you can see time shape, coverage limits, and the paste-ready first query.

NameTypeReqDescription
pack_idstringyesPack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.

No output schema declared.

No examples provided.

get_tool_help ~93

Free blind-caller guidance for one tool visible on this MCP facade. Returns when to use it, what it refuses, a working example, effective access limits, important outputs, provenance fields, recommended next calls, and the shared natural-language-to-strict-JSON interaction contract. Use tools/list to discover names, then call this before an unfamiliar tool.

NameTypeReqDescription
tool_namestringyesExact tool name from tools/list.

No output schema declared.

No examples provided.

get_tsunami_events ~253

Paid x402 canonical tool. Queries tsunamis_events for historical tsunami records and water-height/runup metrics. Best for event counts, max water height thresholds, and top-event lookups. Region filters may use ISO3 country ids or reviewed named-water loc_ids such as IHO1953-240001002 for the Mediterranean Sea; XOO is deprecated. Call without payment first - the server returns HTTP 402 with the exact USDC price before any charge.

NameTypeReqDescription
filtersobjectyesStructured filters including time ranges, region_ids, and compare clauses. Tsunami queries commonly use year-style windows and may use geometry-backed ocean/sea ids such as XSM.
limitintegerMaximum number of rows to return. For largest-wave or latest-event requests, include a narrow time range or region_ids before sorting.
metricsarrayyesMetric ids to return, such as 'event_count', 'max_water_height_m', or event attributes.
outputobjectOptional output controls such as response format hints.
request_idstringOptional caller-supplied request id for tracing and idempotency.
sortOptional sort instructions for row-returning queries.

No output schema declared.

No examples provided.

search_disaster_links ~189

Free linked-disaster discovery helper. Searches published cross-disaster link families by event-type direction, optional via-event type, and optional year window. Use this when you want to discover whether a relationship family exists before you have an exact event id.

NameTypeReqDescription
end_event_typestringOptional ending event type such as tsunami, flood, tornado, or earthquake.
limitintegerMaximum number of matching chains to return. Default 10.
request_idstringOptional caller-supplied request id for tracing.
start_event_typestringOptional starting event type such as earthquake, hurricane, volcano, wildfire, flood, tornado, or tsunami.
via_event_typestringOptional intermediate event type for bounded chain discovery.
year_endintegerOptional inclusive ending year filter.
year_startintegerOptional inclusive starting year filter.

No output schema declared.

No examples provided.

Common questions

What is the DaedalMap Tsunami Data MCP server?

DaedalMap Tsunami Data is an MCP server listed in the public MCP registry as com.daedalmap/tsunamis. Global tsunami events from NOAA NCEI, 2000 BC-present: wave height, runups, and counts. This page covers its hosted endpoint (https://app.daedalmap.com/mcp/tsunamis).

Is the DaedalMap Tsunami Data MCP server safe to use?

DaedalMap Tsunami Data scores 25 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 Tsunami Data MCP server expose?

DaedalMap Tsunami Data exposes 7 tools: get_tool_help, get_catalog, get_pack, get_disaster_links_for_event, get_disaster_link_chain, and 2 more. Their descriptions and schemas cost roughly 1,006 tokens of context every time the server is loaded.

Does the DaedalMap Tsunami Data MCP server require authentication?

No. We connected to DaedalMap Tsunami Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the DaedalMap Tsunami Data MCP server still maintained?

DaedalMap Tsunami Data 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.