mcpbeat Sign in

DaedalMap Flood Events MCP Server

answering

DaedalMap Flood Events is answering right now. Last checked 10 min ago. It exposes 5 tools. Last commit 17 Sep 2026.

Global flood events and extent 1985-present from the Dartmouth Flood Observatory and GFD.

Uptime history 47 days of history · worst day 82%
47 days agonow
96.7%
Uptime 24h
88 of 91 checks
5
Tools
read from the server
277 ms
Response time
average over 24h
2
Stars
last commit 17 Sep 2026

What changed 12

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 August 2026. No other catalogue keeps this.

14 Sep 5 tool descriptions were rewritten get_catalog, get_pack, get_tool_help and 2 more
26 Aug 2 tools changed the parameters they ask for get_pack, query_dataset
14 Aug a tool description was rewritten get_tool_help
14 Aug a tool changed version
12 Aug a tool appeared get_tool_help
12 Aug a tool description was rewritten query_dataset
12 Aug a tool changed version

What the code does

We read the source, 18 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Reads files and sends them to the network mapmover/routes/system.py:2234
    files = sorted(str(p.relative_to(data_dir)) for p in data_dir.rglob("*") if p.is_file())

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add floods --transport http https://app.daedalmap.com/mcp/floods
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "floods": {
      "url": "https://app.daedalmap.com/mcp/floods"
    }
  }
}
~/.codex/config.toml
[mcp_servers.floods]
url = "https://app.daedalmap.com/mcp/floods"
.cursor/mcp.json
{
  "mcpServers": {
    "floods": {
      "url": "https://app.daedalmap.com/mcp/floods"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "floods": {
      "url": "https://app.daedalmap.com/mcp/floods"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

catalog
get_catalog
List the current catalog-published data packs and their access lanes. Start here, then call get_pack for one selected pack.
dataset
query_dataset
Query one catalog-published source or pack with structured metrics, filters, sorting, and a row limit. Call get_catalog and get_pack before an unfamiliar dataset.
disaster
search_disaster_links
Find published cross-hazard relationship families by event type and optional year range before choosing an exact event.
pack
get_pack
Describe one catalog-published pack, including sources, metrics, coverage, freshness, access, and a first query. Call this before querying an unfamiliar pack.
tool
get_tool_help
Describe one tool visible on this facade, including its input contract, access limits, refusals, example, outputs, and recommended next calls.

Endpoints

URLTransportStateLatencyChecked
https://app.daedalmap.com/mcp/floods streamable-http answering 289 ms 10 min ago

Alternatives to DaedalMap Flood Events

same job, measured the same way
DaedalMap Earthquake Data
by daedalmap

Global earthquake events from the USGS, 2150 BC-present: magnitude, depth, location, counts.

8 tools answering
DaedalMap Hurricane and Tropical Cyclone Data
by daedalmap

Global hurricane and tropical cyclone tracks from IBTrACS/NOAA, 1842-present. Wind and pressure.

5 tools answering
DaedalMap Tornado Events
by daedalmap

US tornado events 1950-present from the NOAA Storm Prediction Center: EF rating, tracks, damage.

5 tools answering
Globocan
by pipeworx-io

GLOBOCAN — the IARC/WHO Global Cancer Observatory.

40 tools answering
DaedalMap Historical FX Rates
by daedalmap

Historical FX rates for 100+ currencies vs USD from IMF and World Bank data, 1940-present.

4 tools answering
Gdelt
by pipeworx-io

GDELT MCP — Global Database of Events, Language, and Tone (free, no auth)

35 tools answering
DaedalMap Population Estimates
by daedalmap

Global population estimates from WorldPop, 2000-2030, at country and sub-national levels.

4 tools answering
DaedalMap Volcanic Activity
by daedalmap

Global volcanic eruptions from the Smithsonian Global Volcanism Program: VEI, location, dates.

8 tools answering

DaedalMap Flood Events — questions

Answers built from our own checks of this server.

What can DaedalMap Flood Events do?
It exposes 5 tools, read directly from the server on our last check. Among them: get_catalog, get_pack, get_tool_help, query_dataset, search_disaster_links. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is DaedalMap Flood Events working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 91 checks got a reply (96.7%), average response time 277 ms. The bar chart above shows every period we have measured.
How do I connect DaedalMap Flood Events?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does DaedalMap Flood Events need an API key?
No. DaedalMap Flood Events completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is DaedalMap Flood Events?
It answers our handshake in 277 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is DaedalMap Flood Events open source?
Yes — it is published under the MIT licence, written in Python and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.