DaedalMap Flood Events
by daedalmap.com · remote · no sign-in to list tools · v1.0.1 · published by com.daedalmap
Global flood events and extent 1985-present from the Dartmouth Flood Observatory and GFD.
5 tools: 5 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things0Claude Code: ask
- Only reads5Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http floods https://app.daedalmap.com/mcp/floodsTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
5 tools
Only reads 5Claude Code: allow
get_catalogChoose data or geometry to list published pack IDs or family and scope IDs.No findings
Why it is in this group
- The name "get_catalog" says "get": a word for reading.
Description, as the server wrote it Choose data or geometry to list published pack IDs or family and scope IDs. The response includes a complete catalog download URL. Use get_pack for data or get_geography for geometry. Current catalog: The same geography tools work worldwide across a cataloged baseline of 252 geographic entities, reaching up to Admin 2. Where additional country releases are available, the same calls automatically return deeper administrative tiers or maintained reference families. Additional detail is currently available for Australia, Brazil, Canada, France, Germany, Mexico, United Kingdom, United States.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_dataRetrieve rows from one selected published data pack using exact metrics, loc_id-based region filters, time/metric filters, sorting, and a row limit.No findings
Why it is in this group
- The name "get_data" says "get": a word for reading.
Description, as the server wrote it Retrieve rows from one selected published data pack using exact metrics, loc_id-based region filters, time/metric filters, sorting, and a row limit. Disaster event rows include stable event_id values for get_event drill-down. A parent administrative loc_id selects matching descendant rows at the pack's published grain. Call get_pack first; geometry families use their focused next-step tools.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_eventRetrieve one exact disaster event and explicitly requested relationships, affected places, native observations, or geometry.No findings
Why it is in this group
- The name "get_event" says "get": a word for reading.
Description, as the server wrote it Retrieve one exact disaster event and explicitly requested relationships, affected places, native observations, or geometry. Use get_data to obtain the stable event_id first.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_packInspect one exact data pack ID for its metrics, time coverage, and query metadata before get_data.No findings
Why it is in this group
- The name "get_pack" says "get": a word for reading.
Description, as the server wrote it Inspect one exact data pack ID for its metrics, time coverage, and query metadata before get_data.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_tool_helpDescribe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.No findings
Why it is in this group
- The name "get_tool_help" says "get": a word for reading.
Description, as the server wrote it Describe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http floods https://app.daedalmap.com/mcp/floodsRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__floods__get_tool_help",
"mcp__floods__get_catalog",
"mcp__floods__get_pack",
"mcp__floods__get_event",
"mcp__floods__get_data"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as floods. Review it before you use it.