mcp · Global

com.daedalmap/floods

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

Feature or claim this listing

Feature this listing — founding Featured slots are 50% off for 6 months

Represent com.daedalmap/floods? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Explore paid sponsorship →

What's in it

Data offered llm-inferred: global flood events · flood extent · Dartmouth Flood Observatory flood records · GFD flood records
Coverage llm-inferred: Global · 1985-present
Formats docs-verified: MCP streamable HTTP · JSON
Access llm-inferred: Discovery and small geography lookups are free; some data packs are metered via API key account credit. This pack's access lane is not confirmed (get_catalog reports it). Licence unknown (null in entry).

Useful for

Use cases llm-inferred: Historical flood-event screening for a site in an FRA or flood risk assessment · Flood-extent context for planning or EIA baseline reports · Comparing past flood extents against a drainage strategy or site boundary
Audience llm-inferred: flood consultants · hydrologists · GIS analysts · planners

Limitations

Constraints llm-inferred: Licence and auth are null in the entry; source licence and access terms are unverified · Entry tools list is empty, so the exposed tool names are unverified · Entry URL (/mcp/floods) differs from the documented hosted endpoint (/mcp?registry=github) · Spatial resolution and update frequency are not stated · Upstream sources are Dartmouth Flood Observatory and GFD; the entry does not say whether they are live feeds or archives · Some DaedalMap data packs are metered; this pack's lane must be checked with get_catalog

Licence: Unknown — check provider terms
Authentication: Unknown — review source docs
GitHub stars: 2
Last commit: 16/10/2026
Last successful page check: 14/10/2026
Page health: healthy
Package: Not recorded
Verification: Not independently verified

Auto-extracted, unverified fields: tools, auth. Check upstream documentation.

Provenance & evidence

Listed in official MCP registry; endpoint responded (HTTP 200, MCP endpoints often 4xx on plain GET). Tools not enumerated; run tools/list on connect.

Metadata observed 16/10/2026 · research sweep: registry.modelcontextprotocol.io