Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DaedalMap Hurricane and Tropical Cyclone Data

REMOTE · APP.DAEDALMAP.COM

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

+5 this week 79 Trust /100

Last scanned (13 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1063 tokens (~96/item across 11 items; 5 tools + 6 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +56
    • Injection markers: unverified → pass ▲ security
    • Authorization: unverified → partial ▲ security
    • Transport: fail → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • Stability: unverified → 0.27 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 20 Nov 26 −55
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.20 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 19 Nov 26 +2
    • MCP protocol: fail → pass ▲ functional
    • MCP protocol version: 2025-06-18 → 2026-07-28 functional
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1
    • Tool “get_pack” rewrote its description, which is the text the model reads security
    • Schema quality: 79 → 96 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • “get_pack” added an optional parameter “metrics” cosmetic
    • “get_pack” added an optional parameter “search” cosmetic
    • “get_pack” added an optional parameter “source_id” cosmetic
  • 13 Nov 26 +50
    • Injection markers: unverified → pass ▲ security
    • Authorization: unverified → partial ▲ security
    • Transport: fail → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → fail ▼ functional
    • Schema quality: unverified → 100 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: good functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 95 functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
  • 12 Nov 26 23

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://app.daedalmap.com/mcp/hurricanes?registry=mcpregistry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.daedalmap.com CN=YR2,O=Let's Encrypt,C=US 16 Nov 2026 14 Feb 2027 RSA 2048 SHA256-RSA 5cde8394eddd0e99a1b20787e389bc54747
SANs: app.daedalmap.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

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. DS published 19718 13 Verified
daedalmap.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

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/hurricanes?registry=mcpregistry Verified 200
http (plaintext) http://app.daedalmap.com/mcp/hurricanes?registry=mcpregistry HTTPS enforced 301 https://app.daedalmap.com/mcp/hurricanes?registry=mcpregistry
MCP tools · 5 exposed · ~878 tokens

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 →

Tool Tokens
get_catalog ~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.

NameTypeReqDescription
catalogstringyesRequired directory selector.
NameTypeReqDescription
catalogstring––
catalog_versionstring––
clarificationobject––
detailstring––
download_urlstring––
errorobject––
excluded_countinteger––
familiesarray––
free_get_data_policy_notestring––
generated_atstring|null––
guidanceobject––
next_stepobject––
pack_countinteger––
packsarray––
provenanceobject––
reasonstring––
request_idstring|null––
resolved_queryobject––
result_statusstring––
scopesarray––
tool_familiesarray––
uncertain_countinteger––
uncertain_packsarray––
warningsarray––

No examples provided.

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.

NameTypeReqDescription
filtersobjectyes–
limitinteger–Maximum number of rows to return for the requested source or pack.
metricsarrayyesExact metric ids from get_pack. Use event_count for aggregate counts only when get_pack publishes it.
outputobject–Optional response controls. v1 supports rows only.
pack_idstringyesPack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
request_idstring–Optional caller-supplied request id for tracing and idempotency.
sort––Sort by a sortable field from get_pack; direction defaults to asc.
NameTypeReqDescription
capability_idstring––
clarificationobject––
errorobject––
filters_appliedobject––
guidanceobject––
limitinteger––
next_stepobject––
pack_idstring––
provenanceobject––
query_modestring––
reasonstring––
request_idstring|null––
row_countinteger––
rowsarray––
sortarray––
source_idstring––
truncatedboolean––
warningsarray––

No examples provided.

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.

NameTypeReqDescription
event_idstringyesExact stable event_id returned by a disaster-pack get_data row.
geometry_modestring–current returns the representative/current shape; timeline returns bounded progression frames where supported.
includearray–Optional companion layers. Omit for the lightweight event summary. Geometry is never returned implicitly.
limitinteger–Per-section ceiling for relationships, affected places, observations, or geometry frames.
pack_idstringyesRequired disaster pack_id that returned this event_id from get_data. The tool never searches other packs.
relationship_depthinteger–Bounded cross-hazard traversal depth when relationships is included.
request_idstring–Optional caller-supplied request id for tracing.
source_idstringyesRequired source_id from the same get_data result. Must identify one published event source in pack_id.
NameTypeReqDescription
affected_placesobject––
availableobject––
clarificationobject––
errorobject––
eventobject––
event_idstring––
event_typestring––
geometryobject––
guidanceobject––
includedarray––
next_stepobject––
next_stepsobject––
observationsobject––
pack_idstring––
provenanceobject––
reasonstring––
relationshipsobject––
request_idstring|null––
schema_classstring––
source_idstring––
warningsarray––

No examples provided.

get_pack ~241

Narrow one data pack before get_data. With only pack_id, lists the pack's sources and their coverage. Add source_id to list that source's metrics (name, unit, years, aggregation) and its filterable and sortable fields; search to match metrics across the pack by name, description, or keyword; or metrics for full detail on up to 10 exact ids.

NameTypeReqDescription
metricsarray–Optional. Up to 10 exact metric ids from this pack. Returns full stored detail for each, including description, coverage by era, value statistics, and every source that holds it.
pack_idstringyesPack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
searchstring–Optional. Terms matched against metric ids, names, descriptions, and keywords across this pack's sources; every term must match. Returns up to 25 compact metric lines.
source_idstring–Optional. One source_id from this pack's sources list. Returns every metric in that source with name, unit, years, and aggregation, plus the source's filterable fields, sortable fields, and time fiel…
NameTypeReqDescription
catalogstring––
clarificationobject––
detailstring––
download_callobject––
download_urlstring––
errorobject––
full_callobject––
guidanceobject––
match_countinteger––
material_policyobject––
metricsarray––
next_stepobject––
pack_idstring––
provenanceobject––
query_contractobject––
reasonstring––
request_idstring|null––
sourceobject––
sourcesarray––
truncatedboolean––
unknown_metricsarray––
warningsarray––

No examples provided.

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.

NameTypeReqDescription
questionstring–Optional question used only with a topic overview.
tool_namestring–Exact tool name from tools/list. Do not combine with topic.
topicstring–Workflow overview. Do not combine with tool_name.
NameTypeReqDescription
accessobject––
clarificationobject––
errorobject––
examplesarray––
guidanceobject––
important_output_fieldsarray––
input_schemaobject––
next_stepobject––
okboolean––
provenanceobject––
purposestring––
reasonstring––
recommended_next_callsarray––
request_idstring|null––
titlestring|null––
tool_namestring––
warningsarray––

No examples provided.

Install

How do I install the DaedalMap Hurricane and Tropical Cyclone Data MCP server?

DaedalMap Hurricane and Tropical Cyclone Data is a hosted endpoint at https://app.daedalmap.com/mcp/hurricanes?registry=mcpregistry, 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

# add to Claude Code
claude mcp add --transport http com-daedalmap-hurricanes 'https://app.daedalmap.com/mcp/hurricanes?registry=mcpregistry'
Common questions

What is the DaedalMap Hurricane and Tropical Cyclone Data MCP server?

DaedalMap Hurricane and Tropical Cyclone Data is an MCP server listed in the public MCP registry as com.daedalmap/hurricanes. Global hurricane and tropical cyclone tracks from IBTrACS/NOAA, 1842-present. Wind and pressure. This page covers its hosted endpoint (https://app.daedalmap.com/mcp/hurricanes?registry=mcpregistry).

Is the DaedalMap Hurricane and Tropical Cyclone Data MCP server safe to use?

DaedalMap Hurricane and Tropical Cyclone Data scores 79 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 Hurricane and Tropical Cyclone Data MCP server expose?

DaedalMap Hurricane and Tropical Cyclone Data exposes 5 tools: get_tool_help, get_catalog, get_pack, get_event, get_data. Their descriptions and schemas cost roughly 878 tokens of context every time the server is loaded.

Does the DaedalMap Hurricane and Tropical Cyclone Data MCP server require authentication?

No. We connected to DaedalMap Hurricane and Tropical Cyclone Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the DaedalMap Hurricane and Tropical Cyclone Data MCP server still maintained?

DaedalMap Hurricane and Tropical Cyclone Data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the DaedalMap Hurricane and Tropical Cyclone Data MCP server?

VerifyMCP ran 13 checks on DaedalMap Hurricane and Tropical Cyclone Data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.