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 services.
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, withIf-None-Matchand the User-AgentSanAlert-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.
| Field | What it is |
|---|---|
level |
quiet, activity, approaching, near, no_data or out_of_range |
level_name, say |
the 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, threat |
what raised the level, as the website shows it |
risk, confidence, degraded |
as in the state; degraded means the data may be delayed |
data, no_data_reasons, data_age_s, generated_at |
whether the level can be trusted now, and why not |
place |
the town or the point, its square (cell) and voivodeship |
official |
RCB and RSO messages in force for the voivodeship; null while that cannot be told |
notice, attribution, pass_through |
what has to stay with the data wherever it is shown |
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:
claude mcp add sanalert -- uvx sanalert-mcp
claude 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):
{
"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.pyis the Home Assistant integration'score.py, the same rules in the same words;towns.jsonis the apps' town list (ios/SanAlertKit/Sources/SanAlertKit/Resources/towns-v1.json, made from the website'sweb/src/lib/cities.ts);api_texts.jsonis 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.
Metadata
Release files for sanalert-mcp 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sanalert_mcp-1.0.1.tar.gz | 67.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sanalert_mcp-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.7 kB
Release files / sanalert_mcp-1.0.1.tar.gz
| Download URL | sanalert_mcp-1.0.1.tar.gz |
|---|---|
| Size | 67.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4b9e11497a4ff36188f5283769dde31da0755b1a5828112fb2433a8b6ba6b36
|
|
BLAKE2b-256 checksum How to use checksums |
87ccf34a46bf923a67c63ade04649883f49e9cff5565b9907a02d8413a6413e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / sanalert_mcp-1.0.1-py3-none-any.whl
| Download URL | sanalert_mcp-1.0.1-py3-none-any.whl |
|---|---|
| Size | 20.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
409a0bbe5bdd1c76231ad36af313a42118a0bafdb042ddc39ea30a215d4727e2
|
|
BLAKE2b-256 checksum How to use checksums |
bea93ad34cc31c707ca9d308856f4ab3ded466f3c21d407177cce174a02c08c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for sanalert-mcp 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for sanalert_mcp-1.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.