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 Volcanic Activity

REMOTE · APP.DAEDALMAP.COM

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

0 this week 85 Trust /100

Last scanned (3 hours ago)

Scores higher than 91% of remote servers

Unreachable for 1 day in a row. Last reached 4 Nov 2026.

Category Health and Science

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 Security11
Transport & Reachability0
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.

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.

  • 5 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
  • 4 Nov 26 +3
    • Schema quality: fail → pass ▲ functional
    • Schema quality: excellent → good functional
  • 3 Nov 26 −3
    • Schema quality: pass → fail ▼ functional
    • Schema quality: good → excellent functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 1 Nov 26 +50
    • Stability: unverified → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
  • 31 Oct 26 −50
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 27 Oct 26 +62
    • 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
  • 26 Oct 26 −15
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Transport: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: fail → unverified ▼ functional
  • 25 Oct 26 −47
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 5 Nov 2026 · Probed https://app.daedalmap.com/mcp/volcanoes

TLS unreached
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/volcanoes Unreachable
http (plaintext) http://app.daedalmap.com/mcp/volcanoes HTTPS enforced
MCP tools · 5 exposed · ~689 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––
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 ~52

Inspect one exact data pack ID for its metrics, time coverage, and query metadata before get_data.

NameTypeReqDescription
pack_idstringyesPack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
NameTypeReqDescription
catalogstring––
clarificationobject––
detailstring––
download_callobject––
download_urlstring––
errorobject––
full_callobject––
guidanceobject––
material_policyobject––
next_stepobject––
pack_idstring––
provenanceobject––
reasonstring––
request_idstring|null––
sourcesarray––
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 Volcanic Activity MCP server?

DaedalMap Volcanic Activity is a hosted endpoint at https://app.daedalmap.com/mcp/volcanoes, 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-volcanoes 'https://app.daedalmap.com/mcp/volcanoes'
Common questions

What is the DaedalMap Volcanic Activity MCP server?

DaedalMap Volcanic Activity is an MCP server listed in the public MCP registry as com.daedalmap/volcanoes. Global volcanic eruptions from the Smithsonian Global Volcanism Program: VEI, location, dates. This page covers its hosted endpoint (https://app.daedalmap.com/mcp/volcanoes).

Is the DaedalMap Volcanic Activity MCP server safe to use?

DaedalMap Volcanic Activity scores 85 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 Volcanic Activity MCP server expose?

DaedalMap Volcanic Activity 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 Volcanic Activity MCP server require authentication?

Its publisher declares no required credentials for DaedalMap Volcanic Activity. 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 Volcanic Activity MCP server still maintained?

DaedalMap Volcanic Activity is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.