Ext Ops Panel
Open dashboard
Comparison

SanAlert vs org.gdacs/api

SanAlert is an MCP server published by plrojek. Marketplaces we read that list it: 1 (Official MCP Registry). org.gdacs/api is an MCP server published by gdacs.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceSanAlertorg.gdacs/api
Official MCP Registry Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.1
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

SanAlert vs org.gdacs/api
FactSanAlertorg.gdacs/api
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (sanalert-mcp)Remote server (api.gdacs.org/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/plrojek/sanalert-mcpNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-10-212026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

SanAlert

In its own words, on Official MCP Registry:

Unofficial threat level from the air for a place in Poland, worked out on your own computer.

org.gdacs/api

In its own words, on Official MCP Registry:

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

How to run each

SanAlert As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio sanalert-mcp -- uvx sanalert-mcp

org.gdacs/api As a remote MCP server

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

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only org.gdacs/api has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: SanAlert · What it can do: org.gdacs/api · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built