io.github.matematicsolutions/mcp-saos
NPM · @MATEMATICSOLUTIONS/MCP-SAOS · SCANNED SEP 21
MCP server for Polish court judgments via the SAOS API with verifiable citations.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to matematicsolutions/mcp-saos). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 69 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2361 tokens (~590/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 io.github.matematicsolutions/mcp-saos server?
io.github.matematicsolutions/mcp-saos runs locally as an npm package, launched with npx -y @matematicsolutions/mcp-saos. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @matematicsolutions/mcp-saos
claude mcp add matematicsolutions-mcp-saos -- npx -y @matematicsolutions/mcp-saos
{
"mcpServers": {
"matematicsolutions-mcp-saos": {
"command": "npx",
"args": [
"-y",
"@matematicsolutions/mcp-saos"
]
}
}
} {
"servers": {
"matematicsolutions-mcp-saos": {
"command": "npx",
"args": [
"-y",
"@matematicsolutions/mcp-saos"
]
}
}
} codex mcp add matematicsolutions-mcp-saos -- npx -y @matematicsolutions/mcp-saos
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"matematicsolutions-mcp-saos": {
"type": "local",
"command": [
"npx",
"-y",
"@matematicsolutions/mcp-saos"
],
"enabled": true
}
}
} openclaw mcp add matematicsolutions-mcp-saos --command npx --arg -y --arg @matematicsolutions/mcp-saos
mcp_servers:
matematicsolutions-mcp-saos:
command: "npx"
args: ["-y", "@matematicsolutions/mcp-saos"] {
"McpServers": {
"matematicsolutions-mcp-saos": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@matematicsolutions/mcp-saos"
]
}
}
} assistant mcp add matematicsolutions-mcp-saos -t stdio -c npx -a -y @matematicsolutions/mcp-saos
{
"mcpServers": {
"matematicsolutions-mcp-saos": {
"command": "npx",
"args": [
"-y",
"@matematicsolutions/mcp-saos"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.77 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 · Analysed npm/@matematicsolutions/mcp-saos@1.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | matematicsolutions/mcp-saos |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/matematicsolutions/mcp-saos/.github/workflows/release.yml@refs/tags/v1.2.0 |
| Rekor log index | 2161644618 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:358f40af6539458693920aecd4535930ce01a83082815d0fa3329c4a8c868828b196be87bcad15d394d42674c1d5f31402ae5c2797742360a7349b0ad |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_judgment ~150
Pobiera pelne orzeczenie z SAOS po jego numerycznym ID. Zwraca metadane (sygnatura, sad, data, sklad, podstawy prawne), streszczenie (jesli dostepne) oraz pierwsze 2000 znakow tresci. ID orzeczenia pochodzi z wynikow narzedzia 'search' lub 'search_by_case'. Bledy: `missing_arg` (brak id), `not_found` (id poza baza), `upstream_error`.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string|number | yes | Numeryczne ID orzeczenia w bazie SAOS, np. 352475 lub '31345'. |
No output schema declared.
No examples provided.
saos_cite_check ~447
Citator 'czy wyrok zyje': dla podanej sygnatury szuka POZNIEJSZYCH orzeczen, ktore ja cytuja (pelnotekstowo w SAOS), i skanuje ich uzasadnienia pod frazy przelamania linii orzeczniczej (np. 'odstepuje od pogladu wyrazonego', 'nie podziela pogladu', 'traci moc uchwala', 'uchwala skladu siedmiu sedziow') w oknie ~500 znakow wokol wystapienia sygnatury. Werdykt: przelamanie_wykryte / uchwala_skladu_powiekszonego / nadal_cytowany / brak_cytowan_w_saos. To heurystyka - kazde trafienie ma fragment tekstu do recznej weryfikacji, a brak trafien NIE potwierdza aktualnosci orzeczenia. Bledy: `missing_arg` (nieczytelna sygnatura), `invalid_court_type`, `upstream_error`.
| Name | Type | Req | Description |
|---|---|---|---|
| caseNumber | string | yes | Sygnatura akt orzeczenia do sprawdzenia, np. 'III CZP 6/21'. Moze byc czescia zdania ('uchwala SN z 7.05.2021 r., III CZP 6/21'). |
| courtType | string | – | Opcjonalnie: typ sadu orzeczenia badanego - sygnatury powtarzaja sie miedzy sadami, to doprecyzowuje ktore orzeczenie sprawdzamy. |
| deepScan | boolean | – | Czy pobierac pelne teksty cytujacych orzeczen (domyslnie true). false = tylko szybki skan snippetow z wyszukiwarki. |
| maxScan | number | – | Ile cytujacych orzeczen przeskanowac w pelnym tekscie (1-20, domyslnie 8). Priorytet: SN > uchwaly > najnowsze. |
No output schema declared.
No examples provided.
search ~514
Przeszukuje baze orzeczen sadow polskich w SAOS (System Analizy Orzeczen Sadowych). Pokrycie obejmuje takze orzeczenia biezace (lata 2024-2026 sa dobrze reprezentowane), ale jest nierowne wg typu sadu. Sady administracyjne (WSA/NSA) NIE sa indeksowane. Daty bywaja znieksztalcone przez OCR - weryfikuj sygnature i date w zrodle. Przydatny do: analizy linii orzeczniczej, precedensow, wyszukiwania po tresci / sygnatuze / sedzim / podstawie prawnej. Bledy: `invalid_court_type` (zly enum), `upstream_error` (HTTP/timeout API).
| Name | Type | Req | Description |
|---|---|---|---|
| all | string | – | Wyszukiwanie pelnotekstowe - slowo lub fraza w tresci orzeczenia. |
| caseNumber | string | – | Sygnatura akt, np. 'I ACa 772/13' lub 'IV CSK 123/15'. |
| courtType | string | – | Typ sadu: COMMON=sady powszechne, SUPREME=Sad Najwyzszy, CONSTITUTIONAL_TRIBUNAL=Trybunal Konstytucyjny, NATIONAL_APPEAL_CHAMBER=Krajowa Izba Odwolawcza (KIO). NIE uzywaj ADMINISTRATIVE - sady admin… |
| dateFrom | string | – | Data orzeczenia od (format YYYY-MM-DD), np. '2015-01-01'. |
| dateTo | string | – | Data orzeczenia do (format YYYY-MM-DD), np. '2016-12-31'. |
| judgeName | string | – | Nazwisko sedziego, np. 'Kowalski'. |
| legalBase | string | – | Podstawa prawna, np. 'art. 415 kc' lub 'art. 6 RODO'. |
| pageNumber | number | – | Numer strony (od 0). Do paginacji wynikow. |
| pageSize | number | – | Liczba wynikow na strone (min 10, max 100). Domyslnie 10. |
| referencedRegulation | string | – | Przywolany akt prawny, np. 'ustawa o ochronie danych osobowych'. |
No output schema declared.
No examples provided.
search_by_case ~155
Skrot: szuka orzeczenia po sygnaturze akt (np. 'I ACa 772/13', 'IV CSK 123/15', 'KIO/UZP 100/12'). Odpowiednik search z parametrem caseNumber. Jesli sygnatura nie znajdzie sie w SAOS, sprawa moze byc z sadu administracyjnego (WSA/NSA - nieindeksowane) lub jeszcze nieopublikowana w bazie. Bledy: `missing_arg` (brak caseNumber), `upstream_error`.
| Name | Type | Req | Description |
|---|---|---|---|
| caseNumber | string | yes | Sygnatura akt, np. 'I ACa 772/13'. |
No output schema declared.
No examples provided.
What is the io.github.matematicsolutions/mcp-saos server?
io.github.matematicsolutions/mcp-saos is listed in the public MCP registry as io.github.matematicsolutions/mcp-saos. MCP server for Polish court judgments via the SAOS API with verifiable citations. This page covers its npm package (@matematicsolutions/mcp-saos).
Is the io.github.matematicsolutions/mcp-saos server safe to use?
io.github.matematicsolutions/mcp-saos scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.matematicsolutions/mcp-saos server expose?
io.github.matematicsolutions/mcp-saos exposes 4 tools: search, get_judgment, search_by_case, saos_cite_check. Their descriptions and schemas cost roughly 1,266 tokens of context every time the server is loaded.
Is the io.github.matematicsolutions/mcp-saos server still maintained?
io.github.matematicsolutions/mcp-saos 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.
What licence is the io.github.matematicsolutions/mcp-saos server under?
io.github.matematicsolutions/mcp-saos declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.