org.gdacs/api
REMOTE · API.GDACS.ORG · SCANNED SEP 21
An MCP server that through www.gdacs.org provides access to web‐based disaster information systems.
Available components
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 → Why this is hard to 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 Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the org.gdacs/api MCP server?
org.gdacs/api is a hosted endpoint at https://api.gdacs.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.gdacs.org
claude mcp add --transport http org-gdacs-api 'https://api.gdacs.org/mcp'
{
"mcpServers": {
"org-gdacs-api": {
"url": "https://api.gdacs.org/mcp"
}
}
} {
"servers": {
"org-gdacs-api": {
"type": "http",
"url": "https://api.gdacs.org/mcp"
}
}
} [mcp_servers.org-gdacs-api] url = "https://api.gdacs.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-gdacs-api": {
"type": "remote",
"url": "https://api.gdacs.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-gdacs-api --url 'https://api.gdacs.org/mcp' --transport streamable-http
mcp_servers:
org-gdacs-api:
url: "https://api.gdacs.org/mcp" {
"McpServers": {
"org-gdacs-api": {
"Transport": "http",
"Url": "https://api.gdacs.org/mcp"
}
}
} assistant mcp add org-gdacs-api -t streamable-http -u 'https://api.gdacs.org/mcp'
{
"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.
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.
- 8 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 −1
- Stability: pass → 0.97 functional
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 9 Aug 26 0
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.47 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 8 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.40 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
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 21 Sept 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_active_disasters ~54
Get currently active disasters. Returns events with their geographic footprints grouped by disaster type.
| 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 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.
| 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.
| 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 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.
| 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.
| 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.
| 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.
What is the org.gdacs/api MCP server?
org.gdacs/api is an MCP server listed in the public MCP registry as org.gdacs/api. An MCP server that through www.gdacs.org provides access to web‐based disaster information systems. This page covers its hosted endpoint (https://api.gdacs.org/mcp).
Is the org.gdacs/api MCP server safe to use?
org.gdacs/api scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the org.gdacs/api MCP server expose?
org.gdacs/api exposes 8 tools: get_alert_level_info, search_events, get_disaster_statistics, get_events_by_country, get_event_data, and 3 more. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
Does the org.gdacs/api MCP server require authentication?
No. We connected to org.gdacs/api without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the org.gdacs/api MCP server still maintained?
org.gdacs/api is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.