org.gdacs/api

REMOTE · API.GDACS.ORG · SCANNED AUG 3

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

Available components

+4 this week 71 71 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability82

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 619 tokens (~77/item across 8 items; 8 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.gdacs.org

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

[mcp_servers.org-gdacs-api]
url = "https://api.gdacs.org/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-gdacs-api": {
      "type": "remote",
      "url": "https://api.gdacs.org/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add org-gdacs-api --url https://api.gdacs.org/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  org-gdacs-api:
    url: "https://api.gdacs.org/mcp"

// mcp.json

{
  "mcpServers": {
    "org-gdacs-api": {
      "type": "http",
      "url": "https://api.gdacs.org/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 66

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://api.gdacs.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=*.gdacs.org,O=European Commission,L=Ispra,ST=Varese,C=IT	CN=GlobalSign RSA OV SSL CA 2018,O=GlobalSign nv-sa,C=BE	27 Nov 2025	29 Dec 2026	RSA 2048	SHA256-RSA	2a02f12f6548f492a530f14a
SANs: *.gdacs.org, gdacs.org
CN=GlobalSign RSA OV SSL CA 2018,O=GlobalSign nv-sa,C=BE (CA)	CN=GlobalSign,OU=GlobalSign Root CA - R3,O=GlobalSign	21 Nov 2018	21 Nov 2028	RSA 2048	SHA256-RSA	1ee5f221dfc623bd4333a8557

DNSSEC insecure

Validation of api.gdacs.org. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
org.	present	26974	8	Verified
gdacs.org.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=2592000

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://api.gdacs.org/mcp	Verified	200
http (plaintext)	http://api.gdacs.org/mcp	HTTPS enforced	301	https://api.gdacs.org/mcp

MCP tools — 8 exposed · ~619 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

get_active_disasters ~54

Get currently active disasters. Returns events with their geographic footprints grouped by disaster type.

Input Output Examples

Name	Type	Req	Description
eventTypes	string\|null	—	Optional: semicolon-separated event types to filter (e.g., 'EQ;TC;FL')

No output schema declared.

No examples provided.

get_alert_level_info ~22

Get explanation of GDACS alert level classifications and their meanings.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_disaster_statistics ~92

Get disaster statistics aggregated by event type and alert level for a specified time period.

Input Output Examples

Name	Type	Req	Description
alertLevel	string\|null	—	Alert level filter
country	string\|null	—	Country filter
eventTypes	string\|null	—	Comma-separated event types to include
fromDate	string\|null	—	Start date for statistics period
toDate	string\|null	—	End date for statistics period

No output schema declared.

No examples provided.

get_event_data ~88

Get detailed information about a specific disaster event. Returns event data including location, severity, affected population, and timeline.

Input Output Examples

Name	Type	Req	Description
eventId	integer	yes	Numeric event identifier from GDACS
eventType	string	yes	Event type code: EQ (Earthquake), TC (Tropical Cyclone), FL (Flood), VO (Volcano), WF (Wildfire), DR (Drought)

No output schema declared.

No examples provided.

get_event_types ~21

Get list of all supported disaster event types with their descriptions.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_events_by_country ~73

Get all disaster events affecting a specific country.

Input Output Examples

Name	Type	Req	Description
country	string	yes	Country name or ISO3 code
daysBack	integer	—	Number of days to look back (default 30, max 365)
limit	integer	—	Maximum number of results (default 50, max 100)

No output schema declared.

No examples provided.

get_recent_alerts ~66

Get list of recent disaster alerts from the last N hours.

Input Output Examples

Name	Type	Req	Description
hours	integer	—	Number of hours to look back (default 24, max 168)
minAlertLevel	string\|null	—	Minimum alert level: 'green', 'orange', or 'red'

No output schema declared.

No examples provided.

search_events ~203

Search for disaster events with various filters. Returns a list of events matching the criteria, ordered by date descending.

Input Output Examples

Name	Type	Req	Description
alertLevel	string\|null	—	Alert level filter: 'green', 'orange', 'red', or combination like 'orange;red'
country	string\|null	—	Filter by country name or ISO code
eventTypes	string\|null	—	Comma-separated event types to include (e.g., 'EQ,TC,FL'). Leave empty for all types.
eventname	string\|null	—	Filter by eventame, tipically for the TC, cyclone name
fromDate	string\|null	—	Start date for search range (ISO 8601 format)
limit	integer	—	Maximum number of results to return (1-100, default 20)
minSeverity	number\|null	—	Minimum severity value to filter
toDate	string\|null	—	End date for search range (ISO 8601 format)

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	66
27 Jul	67
28 Jul	68
29 Jul	68
30 Jul	69
31 Jul	69
1 Aug	70
2 Aug	70
3 Aug	71