Remote MCP · Endpoint

DaedalMap Tsunami Data MCP server

No. DaedalMap Tsunami Data answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.daedalmap.com/mcp/tsunamis

The last check completed an MCP handshake.

Registry name
com.daedalmap/tsunamis
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
23 ms
Tools exposed
5 tools
Uptime, last 30 days
82.4% from 17 checks
Described by its publisher as
Global tsunami events from NOAA NCEI, 2000 BC-present: wave height, runups, and counts.
Listing
From the official MCP registry (active).
Recent checks of DaedalMap Tsunami Data
CheckedResultHandshake
1 hour agoHandshake completed23 ms
2 days agoHandshake completed10 ms
4 days agoHandshake completed16 ms
5 days agoHandshake completed10 ms
7 days agoHandshake completed20 ms
8 days agoHandshake completed11 ms
9 days agoHandshake completed11 ms
12 days agoHandshake completed11 ms
14 days agoFailed - the check failed for an unclassified reason—
15 days agoHandshake completed10 ms
17 days agoHandshake completed30 ms
18 days agoHandshake completed20 ms
19 days agoHandshake completed11 ms
20 days agoHandshake completed13 ms
20 days agoHandshake completed13 ms
22 days agoFailed - the check failed for an unclassified reason—
23 days agoFailed - the check failed for an unclassified reason—

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with DaedalMap Tsunami Data and makes no claim about it beyond what these checks measured.