GDACS MCP server
Featured official server
8 tools · Last check that passed 4 Nov 2026, 12:15 UTC
GDACS's own remote MCP server gives an agent GDACS disaster alerts and event data, covering earthquakes, tropical cyclones, floods, volcanoes, droughts and forest fires, from the cooperation framework of the United Nations and the European Commission. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 8 tools
| Tool | Counted as |
|---|---|
get_active_disasters | Said to only read |
get_alert_level_info | Said to only read |
get_disaster_statistics | Said to only read |
get_event_data | Said to only read |
get_event_types | Said to only read |
get_events_by_country | Said to only read |
get_recent_alerts | Said to only read |
search_events | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
21 of the last 21 checks passed
A check passes when the server lists its tools. Checked at https://api.gdacs.org/mcp.
Recent changes
No change seen across the last 21 checks that passed.
From the scan of 4 Nov 2026, 12:43 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when GDACS's tools change.
One email when GDACS's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- GDACS says its products are model results, calculated by semi-automatic algorithms from scientific and official data, and that its data can change often and without notice. GDACS's disclaimer and terms of use
- GDACS says its notifications for earthquakes, tsunamis and tropical cyclones are produced by algorithms and not reviewed by human experts before they are issued, and may contain uncertainties and errors. GDACS's disclaimer and terms of use
- GDACS says its services do not replace official alerts from local or national disaster authorities, and that only those authorities can order evacuations. GDACS's disclaimer and terms of use
How to limit it
With GDACS's own settings, as its documentation describes them. Stackduke has not tested them.
- Confirm a GDACS alert or impact estimate with the official alert providers or national authorities before acting on it, as GDACS advises. GDACS's disclaimer and terms of use
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.