Skip to content

gdacs.org MCP server

org.gdacs/apigdacs.orgstreamable-httpv1.0.1Scanned

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

8 tools: 8 only read.

Tools: 0 delete, 0 irreversible, 0 write, 8 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the gdacs.org MCP server can do

The gdacs.org MCP server is published by gdacs.org, a domain the MCP Registry verified. It has 8 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Only reads 8Show 8 read-only tools
  • get_active_disastersGet currently active disasters.No findings

    Why it is in this group

    • The name "get_active_disasters" says "get": a word for reading.
    Description, as the server wrote it
    Get currently active disasters. Returns events with their geographic footprints grouped by disaster type.
  • get_alert_level_infoGet explanation of GDACS alert level classifications and their meanings.No findings

    Why it is in this group

    • The name "get_alert_level_info" says "get": a word for reading.
    Description, as the server wrote it
    Get explanation of GDACS alert level classifications and their meanings.
  • get_disaster_statisticsGet disaster statistics aggregated by event type and alert level for a specified time period.No findings

    Why it is in this group

    • The name "get_disaster_statistics" says "get": a word for reading.
    Description, as the server wrote it
    Get disaster statistics aggregated by event type and alert level for a specified time period.
  • get_event_dataGet detailed information about a specific disaster event.No findings

    Why it is in this group

    • The name "get_event_data" says "get": a word for reading.
    Description, as the server wrote it
    Get detailed information about a specific disaster event. Returns event data including location, severity, affected population, and timeline.
  • get_event_typesGet list of all supported disaster event types with their descriptions.No findings

    Why it is in this group

    • The name "get_event_types" says "get": a word for reading.
    Description, as the server wrote it
    Get list of all supported disaster event types with their descriptions.
  • get_events_by_countryGet all disaster events affecting a specific country.No findings

    Why it is in this group

    • The name "get_events_by_country" says "get": a word for reading.
    Description, as the server wrote it
    Get all disaster events affecting a specific country.
  • get_recent_alertsGet list of recent disaster alerts from the last N hours.No findings

    Why it is in this group

    • The name "get_recent_alerts" says "get": a word for reading.
    Description, as the server wrote it
    Get list of recent disaster alerts from the last N hours.
  • search_eventsSearch for disaster events with various filters.No findings

    Why it is in this group

    • The name "search_events" says "search": a word for reading.
    Description, as the server wrote it
    Search for disaster events with various filters. Returns a list of events matching the criteria, ordered by date descending.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http api https://api.gdacs.org/mcp
claude mcp add --transport http api https://api.gdacs.org/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__api__get_alert_level_info",
      "mcp__api__search_events",
      "mcp__api__get_disaster_statistics",
      "mcp__api__get_events_by_country",
      "mcp__api__get_event_data",
      "mcp__api__get_recent_alerts",
      "mcp__api__get_active_disasters",
      "mcp__api__get_event_types"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as api. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/org.gdacs/api/verify?hash=060711cc461e772156edd6586115fd7201197353a52bea95aa2fbeeaca24fcec" | jq -e '.changed == false'

Pinned hash 060711cc461e, from Nov 19, 2026, 01:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/org.gdacs/api/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for org.gdacs/api
[![Anlyon Radar](https://radar.anlyon.com/badge/org.gdacs/api.svg)](https://radar.anlyon.com/servers/org.gdacs/api)

Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.

gdacs.org MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the gdacs.org MCP server safe?

No scan can promise that. What its definitions show: 8 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the gdacs.org MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the gdacs.org MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the gdacs.org MCP server have?

8 tools: 8 read. get_alert_level_info, search_events, get_disaster_statistics, get_events_by_country, get_event_data, get_recent_alerts, get_active_disasters and get_event_types.

Does the gdacs.org MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the gdacs.org MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the gdacs.org MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.