Remote MCP · Endpoint

DaedalMap Flood Events MCP server

No. DaedalMap Flood Events answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

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

The last check completed an MCP handshake.

Registry name
com.daedalmap/floods
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
19 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Global flood events and extent 1985-present from the Dartmouth Flood Observatory and GFD.
Website
https://www.daedalmap.com/
Repository
https://github.com/xyver/daedal-map
Listing
From the official MCP registry (active).
Recent checks of DaedalMap Flood Events
CheckedResultHandshake
1 day agoHandshake completed19 ms
3 days agoHandshake completed20 ms
5 days agoHandshake completed21 ms
6 days agoHandshake completed40 ms
7 days agoHandshake completed30 ms
9 days agoHandshake completed23 ms
11 days agoHandshake completed355 ms
13 days agoHandshake completed31 ms
15 days agoHandshake completed11 ms
16 days agoHandshake completed13 ms
17 days agoHandshake completed11 ms
18 days agoHandshake completed12 ms
19 days agoHandshake completed77 ms
20 days agoHandshake completed12 ms
21 days agoHandshake completed42 ms
22 days agoHandshake completed12 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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