SanAlert

io.github.plrojekPublished by GitHub account plrojekv1.1.0Updated Nov 3, 2026

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

The publisher's own server: Alertcamp

VerifiedSTDIODesktop only

Overview

SanAlert's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open SanAlert in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

SanAlert for AI assistants

The unofficial threat level from the air for a place in Poland, for an AI assistant that can run a local MCP server (Claude Code, Claude Desktop and others). Ask it "what is the level in Przemyśl?" and the assistant gets the answer the website would show for that place. Not an official warning system: it does not replace sirens, Alert RCB or instructions from the authorities.

What it does, and what it sends

  • It runs on your computer and talks to the assistant over stdio.
  • When the assistant asks about a place, it fetches https://api.sanalert.pl/v1/state, the same public document the website and the apps read: at most once every 5 s, with If-None-Match and the User-Agent SanAlert-MCP/<version>. Once per run it fetches the public grid (/v1/grid/1.json) to find the place's ~11 km square and its voivodeship.
  • It looks the place's level up in that document with the rules SanAlert's website and apps follow (sanalert.pl/jak-to-dziala). The place stays on your computer: no request carries it, and a town's name is never looked up online.
  • The privacy page says the same (sanalert.pl/prywatnosc, "Serwer SanAlert dla asystentów AI"). Terms (Regulamin, Умови).

The tool

sanalert_level takes place, one of the website's towns (Przemyśl, Lublin, Rzeszów, Chełm and the rest of its list; Polish letters optional, and Warsaw and Cracow work too), or latitude and longitude, and language: pl, en or uk.

FieldWhat it is
levelquiet, activity, approaching, near, no_data or out_of_range
level_name, saythe level's name and the website's sentence under it, in the chosen language
reason_code, kind, km, eta_min, course_known, lost_at, oblast, raion, threatwhat raised the level, as the website shows it
risk, confidence, degradedas in the state; degraded means the data may be delayed
data, no_data_reasons, no_data_codes, data_age_s, generated_at, expires_atwhether the level can be trusted now, and why not: no_data_codes (1.1.0) are not_ready, stale, levels_not_valid, health_unknown (as the remote server's), grid_unreadable, state_unreadable, no_time, unknown_level; after expires_at (generated_at + 60 s) the answer is no data
placethe town or the point, its square (cell) and voivodeship
officialRCB and RSO messages in force for the voivodeship; null while that cannot be told. Since 1.1.0 each also has the remote server's class, text, regions_in_force and powiats
notice, attribution, pass_throughwhat has to stay with the data wherever it is shown

The towns place accepts are also a resource, sanalert://towns (1.1.0), with their coordinates.

Blind is not calm. When the document is missing, cannot be read or is older than 60 s, or the grid cannot be read, the level is no_data, never quiet, and say says so. The age is never less than the time the server has held the document, so a computer clock that runs behind cannot keep an old "quiet" fresh while the API is down. A point outside Poland's grid is out_of_range. A name that is not on the list is an error that names the list: give coordinates instead.

For the whole of Poland (the state summarised, official messages of the last 24 hours, night reports, the reliability record) SanAlert runs a remote MCP server, https://api.sanalert.pl/mcp. It takes no place.

Install

It needs uv.

Claude Code:

sh
claude mcp add sanalert -- uvx sanalert-mcpclaude mcp add --transport http sanalert-poland https://api.sanalert.pl/mcp      # optional: the whole of Poland

Or both at once, as a Claude Code plugin: /plugin marketplace add plrojek/agent-skills, then /plugin install sanalert@plrojek. Straight from GitHub instead of PyPI: uvx --from git+https://github.com/plrojek/sanalert-mcp sanalert-mcp.

Claude Desktop (claude_desktop_config.json):

json
{  "mcpServers": {    "sanalert": {      "command": "uvx",      "args": ["sanalert-mcp"]    }  }}

Conditions of use

Whoever shows or repeats the data keeps notice visible with it and a visible link to every attribution entry, always refers readers to the official air-raid alarms (sirens, Alert RCB, the instructions of the authorities), keeps a visible link to NEPTUN (https://neptun.in.ua, for example "Дані: Карта повітряних тривог — NEPTUN") next to the level, never turns no data into quiet, and says that the level is SanAlert's inference, not an official warning. In full: terms and the API description.

Development

uv run pytest runs the tests; none of them goes online.

Three files in src/sanalert_mcp/ are generated, never edited by hand:

  • core.py is the Home Assistant integration's core.py, the same rules in the same words;
  • towns.json is the apps' town list (ios/SanAlertKit/Sources/SanAlertKit/Resources/towns-v1.json, made from the website's web/src/lib/cities.ts);
  • api_texts.json is the API's notice, attribution and pass-through (api/sanalert/state.py, api/sanalert/mcp_server.py).

python scripts/sync.py copies the first two and python scripts/sync.py --check fails on any difference (CI runs it). The API's tests fail when api_texts.json no longer matches the API.

The source is integrations/mcp/ in SanAlert's own repository; the public repository (github.com/plrojek/sanalert-mcp) is a copy of it, refreshed with each release, so a fix in core.py reaches users with the next release.

License

MIT, Applied AI sp. z o.o.

Source: README.md at commit f71d99a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.1.0LatestNov 3, 2026
  2. v1.0.1Oct 21, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Alert integrations