← All servers

DaedalMap Tsunami Data

warnings

app.daedalmap.com

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

https://app.daedalmap.com/mcp/tsunamisWebsiteUnknownMCP 2025-06-18v0.4.0last checked 8 Oct 2026spoke MCP on 100% of 91 checks (30 days)initialize in 245 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

–Claude CodeUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Claude Code docs · read on 2026-08-30

–Claude (claude.ai & Desktop)Unknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

–ChatGPTUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

ChatGPT docs · read on 2026-08-30

–CursorUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Cursor docs · read on 2026-08-30

–VS Code (Copilot)Unknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 8 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme
Unknown
Protected-resource metadata
✕Not found

Without it a client has to guess where the authorization server lives.

Anonymous access
Refused — credentials required

What the probe found

warningThe server refused to initialize

It speaks JSON-RPC but rejected the handshake: "The MCP service is receiving requests too quickly. Retry after the indicated delay."

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

get_catalogget_dataget_eventget_packget_tool_help

Contract history

28 Sep 2026v0.4.05 breaking4 compatible1 cosmeticinstructions rewritten

Breaking: get_disaster_link_chain, get_disaster_links_for_event, get_tool_help, get_tsunami_events, search_disaster_links

Instructions rewritten: get_catalog, get_pack, get_tool_help. The description an agent follows changed; the callable contract may not have.

26 Aug 2026v0.4.01 cosmetic
24 Aug 2026v0.4.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge for DaedalMap Tsunami Data
[![MCP status](https://mcpi.app/servers/daedalmap-tsunami-data/badge.svg)](https://mcpi.app/servers/daedalmap-tsunami-data)