DaedalMap Flood Events
REMOTE · APP.DAEDALMAP.COM
Global flood events and extent 1985-present from the Dartmouth Flood Observatory and GFD.
Available components
Last scanned (23 hours ago)
Scores higher than 89% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 30 Oct 26 +61
- Stability: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 29 Oct 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 28 Oct 26 +51
- Stability: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 27 Oct 26 −51
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 22 Oct 26 +4
No change was recorded against any check on this day. Stability & Change Management went from 48 to 78.
- 17 Oct 26 −2
- A breaking change shipped without a version bump: still 0.4.0 ▼ security
- Tool “get_catalog” rewrote its description, which is the text the model reads security
- Tool “get_pack” rewrote its description, which is the text the model reads security
- “get_catalog” made “catalog” required, so existing callers break ▼ functional
- Schema quality: 105 → 80 ▲ functional
- “get_catalog” reworded the description of “catalog” cosmetic
- “get_catalog” dropped the optional parameter “country_scope” cosmetic
- “get_catalog” dropped the optional parameter “detail” cosmetic
- “get_catalog” dropped the optional parameter “loc_id” cosmetic
- “get_catalog” dropped the optional parameter “time_range” cosmetic
- “get_pack” dropped the optional parameter “catalog” cosmetic
- “get_pack” dropped the optional parameter “country_scope” cosmetic
- “get_pack” dropped the optional parameter “detail” cosmetic
- “get_pack” dropped the optional parameter “release_unit” cosmetic
- Tool “get_catalog” changed its title: List Available Packs and Geometry Families → List Published Packs or Geographies cosmetic
- Tool “get_pack” changed its title: Inspect One Selected Pack or Geometry Family → Inspect One Data Pack cosmetic
- 16 Oct 26 0
- A breaking change shipped without a version bump: still 0.4.0 ▼ security
- “get_event” added a required parameter “source_id”, so existing callers break ▼ functional
- “get_event” made “pack_id” required, so existing callers break ▼ functional
- “get_event” reworded the description of “pack_id” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://app.daedalmap.com/mcp/floods
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.daedalmap.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| daedalmap.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.daedalmap.com/mcp/floods | Unreachable | ||
| http (plaintext) | http://app.daedalmap.com/mcp/floods | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_catalog List Published Packs or Geographies ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | string | yes | Required directory selector. |
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | string | – | – |
| catalog_version | string | – | – |
| clarification | object | – | – |
| detail | string | – | – |
| download_url | string | – | – |
| error | object | – | – |
| excluded_count | integer | – | – |
| families | array | – | – |
| generated_at | string|null | – | – |
| guidance | object | – | – |
| next_step | object | – | – |
| pack_count | integer | – | – |
| packs | array | – | – |
| provenance | object | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| resolved_query | object | – | – |
| result_status | string | – | – |
| scopes | array | – | – |
| tool_families | array | – | – |
| uncertain_count | integer | – | – |
| uncertain_packs | array | – | – |
| warnings | array | – | – |
No examples provided.
get_data Get Data ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | yes | – |
| limit | integer | – | Maximum number of rows to return for the requested source or pack. |
| metrics | array | yes | Exact metric ids from get_pack. Use event_count for aggregate counts only when get_pack publishes it. |
| output | object | – | Optional response controls. v1 supports rows only. |
| pack_id | string | yes | Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change. |
| request_id | string | – | Optional caller-supplied request id for tracing and idempotency. |
| sort | – | – | Sort by a sortable field from get_pack; direction defaults to asc. |
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | – | – |
| clarification | object | – | – |
| error | object | – | – |
| filters_applied | object | – | – |
| guidance | object | – | – |
| limit | integer | – | – |
| next_step | object | – | – |
| pack_id | string | – | – |
| provenance | object | – | – |
| query_mode | string | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| row_count | integer | – | – |
| rows | array | – | – |
| sort | array | – | – |
| source_id | string | – | – |
| truncated | boolean | – | – |
| warnings | array | – | – |
No examples provided.
get_event Get Event ~215
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | Exact stable event_id returned by a disaster-pack get_data row. |
| geometry_mode | string | – | current returns the representative/current shape; timeline returns bounded progression frames where supported. |
| include | array | – | Optional companion layers. Omit for the lightweight event summary. Geometry is never returned implicitly. |
| limit | integer | – | Per-section ceiling for relationships, affected places, observations, or geometry frames. |
| pack_id | string | yes | Required disaster pack_id that returned this event_id from get_data. The tool never searches other packs. |
| relationship_depth | integer | – | Bounded cross-hazard traversal depth when relationships is included. |
| request_id | string | – | Optional caller-supplied request id for tracing. |
| source_id | string | yes | Required source_id from the same get_data result. Must identify one published event source in pack_id. |
| Name | Type | Req | Description |
|---|---|---|---|
| affected_places | object | – | – |
| available | object | – | – |
| clarification | object | – | – |
| error | object | – | – |
| event | object | – | – |
| event_id | string | – | – |
| event_type | string | – | – |
| geometry | object | – | – |
| guidance | object | – | – |
| included | array | – | – |
| next_step | object | – | – |
| next_steps | object | – | – |
| observations | object | – | – |
| pack_id | string | – | – |
| provenance | object | – | – |
| reason | string | – | – |
| relationships | object | – | – |
| request_id | string|null | – | – |
| schema_class | string | – | – |
| source_id | string | – | – |
| warnings | array | – | – |
No examples provided.
get_pack Inspect One Data Pack ~52
Inspect one exact data pack ID for its metrics, time coverage, and query metadata before get_data.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_id | string | yes | Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change. |
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | string | – | – |
| clarification | object | – | – |
| detail | string | – | – |
| download_call | object | – | – |
| download_url | string | – | – |
| error | object | – | – |
| full_call | object | – | – |
| guidance | object | – | – |
| material_policy | object | – | – |
| next_step | object | – | – |
| pack_id | string | – | – |
| provenance | object | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| sources | array | – | – |
| warnings | array | – | – |
No examples provided.
get_tool_help Get Tool Help ~84
Describe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | – | Optional question used only with a topic overview. |
| tool_name | string | – | Exact tool name from tools/list. Do not combine with topic. |
| topic | string | – | Workflow overview. Do not combine with tool_name. |
| Name | Type | Req | Description |
|---|---|---|---|
| access | object | – | – |
| clarification | object | – | – |
| error | object | – | – |
| examples | array | – | – |
| guidance | object | – | – |
| important_output_fields | array | – | – |
| input_schema | object | – | – |
| next_step | object | – | – |
| ok | boolean | – | – |
| provenance | object | – | – |
| purpose | string | – | – |
| reason | string | – | – |
| recommended_next_calls | array | – | – |
| request_id | string|null | – | – |
| title | string|null | – | – |
| tool_name | string | – | – |
| warnings | array | – | – |
No examples provided.
How do I install the DaedalMap Flood Events MCP server?
DaedalMap Flood Events is a hosted endpoint at https://app.daedalmap.com/mcp/floods, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.daedalmap.com
claude mcp add --transport http com-daedalmap-floods 'https://app.daedalmap.com/mcp/floods'
What is the DaedalMap Flood Events MCP server?
DaedalMap Flood Events is an MCP server listed in the public MCP registry as com.daedalmap/floods. Global flood events and extent 1985-present from the Dartmouth Flood Observatory and GFD. This page covers its hosted endpoint (https://app.daedalmap.com/mcp/floods).
Is the DaedalMap Flood Events MCP server safe to use?
DaedalMap Flood Events scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DaedalMap Flood Events MCP server expose?
DaedalMap Flood Events exposes 5 tools: get_tool_help, get_catalog, get_pack, get_event, get_data. Their descriptions and schemas cost roughly 689 tokens of context every time the server is loaded.
Does the DaedalMap Flood Events MCP server require authentication?
Its publisher declares no required credentials for DaedalMap Flood Events. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the DaedalMap Flood Events MCP server still maintained?
DaedalMap Flood Events is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.