Mcp

DaedalMap Tsunami Data

Geographic-query MCP lane for historical tsunami event data, sourced from NOAA's 2.6K-event tsunami catalog (2000 BC - present). Part of the broader DaedalMap engine — map-first runtime that lets an agent answer "show tsunamis for a place and time window" without assembling a GIS pipeline.

Verified: 2026-05-13 (mcp-registry-ingest-2026-05-13+enrich-capability-skill)

When to use DaedalMap Tsunami Data

Choose if

You're building a research, journalism, or insurance-related agent that needs to answer "what tsunamis happened near X in time range Y" with a structured response — and you want NOAA's authoritative catalog (2.6K events, 2000 BC - present) rather than scraping Wikipedia. Map-first design also helps when the agent needs to compose tsunami events with population or economic context from DaedalMap's other packs.

Avoid if

You need real-time tsunami warnings (this is historical event data, not USGS NOAA alerts feeds) or live forecasts. Also avoid if you need just earthquakes — use com.olyport/earthquake or USGS directly; tsunamis are much rarer events. Self-host setup is non-trivial (DuckDB + parquet + LLM key + pack management) — prefer the hosted MCP unless you need data sovereignty.

Risk Flags

  • LOW scope Single-dataset lane (tsunamis only). DaedalMap itself ships 40+ source packs (earthquakes, hurricanes, wildfires, floods, etc.) — but this MCP record is scoped to the tsunami lane. For multi-disaster queries you need DaedalMap's broader runtime, not just this MCP.
  • MEDIUM runtime Self-host README states the paid execution lane returns `commercial_access_unavailable` unless a commercial verifier is configured. The hosted MCP may require API-key/entitlement; pricing not published in the public registry entry.

Cost

Type: Unknown

Distribution

MCP Registry
com.daedalmap/tsunamis
Repository
https://github.com/xyver/daedal-map