mcpbeat

Gdacs MCP Server

org.gdacs/api
answering

Gdacs is answering right now. Last checked 12 min ago. It exposes 8 tools.

An MCP server that through www.gdacs.org provides access to web‐based disaster information systems.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
353 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add api --transport http https://api.gdacs.org/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "api": {
      "url": "https://api.gdacs.org/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.api]
url = "https://api.gdacs.org/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "api": {
      "url": "https://api.gdacs.org/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "api": {
      "url": "https://api.gdacs.org/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

event
get_event_data
Get detailed information about a specific disaster event. Returns event data including location, severity, affected population, and timeline.
get_event_types
Get list of all supported disaster event types with their descriptions.
events
get_events_by_country
Get all disaster events affecting a specific country.
search_events
Search for disaster events with various filters. Returns a list of events matching the criteria, ordered by date descending.
active
get_active_disasters
Get currently active disasters. Returns events with their geographic footprints grouped by disaster type.
alert
get_alert_level_info
Get explanation of GDACS alert level classifications and their meanings.
disaster
get_disaster_statistics
Get disaster statistics aggregated by event type and alert level for a specified time period.
recent
get_recent_alerts
Get list of recent disaster alerts from the last N hours.

Endpoints

URLTransportStateLatencyChecked
https://api.gdacs.org/mcp streamable-http answering 423 ms 12 min ago

Gdacs — questions

Answers built from our own checks of this server.

What can Gdacs do?
It exposes 8 tools, read directly from the server on our last check. Among them: get_active_disasters, get_alert_level_info, get_disaster_statistics, get_event_data, get_events_by_country, get_event_types and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Gdacs mostly used for?
Its tools cluster around event and events. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Gdacs working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 353 ms. The bar chart above shows every period we have measured.
How do I connect Gdacs?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Gdacs need an API key?
No. Gdacs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Gdacs?
It answers our handshake in 353 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.