Remote MCP · Endpoint

Gdacs MCP server

No. Gdacs answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/gdacs/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/gdacs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
212 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
GDACS MCP — Global Disaster Alert and Coordination System.
Listing
From the official MCP registry (active).
Recent checks of Gdacs
CheckedResultHandshake
1 hour agoHandshake completed212 ms
22 hours agoHandshake completed217 ms
2 days agoHandshake completed213 ms
3 days agoHandshake completed157 ms
4 days agoHandshake completed86 ms
5 days agoHandshake completed107 ms
6 days agoHandshake completed233 ms
8 days agoHandshake completed86 ms
11 days agoHandshake completed66 ms
13 days agoHandshake completed79 ms
16 days agoHandshake completed98 ms
18 days agoHandshake completed67 ms
20 days agoHandshake completed66 ms
22 days agoHandshake completed64 ms
24 days agoHandshake completed67 ms
26 days agoHandshake completed91 ms
27 days agoHandshake completed174 ms
29 days agoHandshake completed50 ms

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

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 Gdacs and makes no claim about it beyond what these checks measured.