Remote MCP · Endpoint

DaedalMap Volcanic Activity MCP server

No. DaedalMap Volcanic Activity answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://app.daedalmap.com/mcp/volcanoes

The last check completed an MCP handshake.

Registry name
com.daedalmap/volcanoes
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
19 ms
Tools exposed
5 tools
Uptime, last 30 days
68.8% from 16 checks
Described by its publisher as
Global volcanic eruptions from the Smithsonian Global Volcanism Program: VEI, location, dates.
Listing
From the official MCP registry (active).
Recent checks of DaedalMap Volcanic Activity
CheckedResultHandshake
1 day agoHandshake completed19 ms
3 days agoHandshake completed13 ms
5 days agoHandshake completed11 ms
6 days agoHandshake completed14 ms
7 days agoHandshake completed13 ms
9 days agoFailed - the check failed for an unclassified reason—
11 days agoHandshake completed157 ms
13 days agoHandshake completed23 ms
15 days agoHandshake completed19 ms
16 days agoHandshake completed13 ms
17 days agoHandshake completed14 ms
18 days agoHandshake completed10 ms
19 days agoFailed - the check failed for an unclassified reason—
20 days agoFailed - the check failed for an unclassified reason—
21 days agoFailed - the check failed for an unclassified reason—
22 days agoFailed - the check failed for an unclassified reason—

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with DaedalMap Volcanic Activity and makes no claim about it beyond what these checks measured.