io.github.matematicsolutions/prawo-pl-mcp
PYPI · PRAWO-PL-MCP · SCANNED SEP 20
One MCP server for Polish legal data - courts, legislation, KRS, tax, KIO, UODO via 4 unified tools
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 14 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 26 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2145 tokens (~429/item across 5 items; 5 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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/prawo-pl-mcp server?
io.github.matematicsolutions/prawo-pl-mcp runs locally as a PyPI package, launched with uvx prawo-pl-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · prawo-pl-mcp
claude mcp add matematicsolutions-prawo-pl-mcp -- uvx prawo-pl-mcp
{
"mcpServers": {
"matematicsolutions-prawo-pl-mcp": {
"command": "uvx",
"args": [
"prawo-pl-mcp"
]
}
}
} {
"servers": {
"matematicsolutions-prawo-pl-mcp": {
"command": "uvx",
"args": [
"prawo-pl-mcp"
]
}
}
} codex mcp add matematicsolutions-prawo-pl-mcp -- uvx prawo-pl-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"matematicsolutions-prawo-pl-mcp": {
"type": "local",
"command": [
"uvx",
"prawo-pl-mcp"
],
"enabled": true
}
}
} openclaw mcp add matematicsolutions-prawo-pl-mcp --command uvx --arg prawo-pl-mcp
mcp_servers:
matematicsolutions-prawo-pl-mcp:
command: "uvx"
args: ["prawo-pl-mcp"] {
"McpServers": {
"matematicsolutions-prawo-pl-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"prawo-pl-mcp"
]
}
}
} assistant mcp add matematicsolutions-prawo-pl-mcp -t stdio -c uvx -a prawo-pl-mcp
{
"mcpServers": {
"matematicsolutions-prawo-pl-mcp": {
"command": "uvx",
"args": [
"prawo-pl-mcp"
]
}
}
} 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 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.
- 17 Sept 26 +1
- Package version: 0.1.3 → 0.2.3 functional
- 15 Sept 26 −2
- Stability: pass → 0.80 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 13 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.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 7 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 20 Sept 2026 · Analysed pypi/prawo-pl-mcp@0.2.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 14 packages
| Packages resolved | 14 |
|---|---|
| Stale | 1 |
| 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 →
pl_call ~244
Escape hatch: call any native tool of any registered source. For operations the unified tools do not cover: citator (saos_cite_check), DPA statistics (uodo_stats), procurement-article search (kio_by_pzp_article), board composition (get_board), regulation comparison (eu_compare), tax category dictionary (list_categories)... `arguments` (alias: `args` - both accepted, pass only one) is an object keyed by the NATIVE parameter names of that tool, passed verbatim. The native names of the common ones are in `native_params` from pl_list_sources; for everything else read the live schema via pl_list_sources(source_id=...). Wrong parameter names are caught here against the connector's schema, before the call leaves the aggregator. Errors: `unknown_source`, `unknown_tool` (not exposed by that source), `invalid_arg` (missing required or misspelled parameter name), `source_unavailable`, `upstream_error` (connector's own error code in message).
| Name | Type | Req | Description |
|---|---|---|---|
| args | – | – | – |
| arguments | – | – | – |
| source | string | yes | – |
| tool | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pl_coverage ~102
Declare what this connector covers, how it is sourced, and what it does NOT cover. Call this before telling a user that the law "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the law. Every gap carries a fallback saying where to look instead. Returns: ``Coverage`` with families, an as-of note, and a non-empty list of known gaps.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_note | string | yes | States what the dates mean, and what they do not promise. |
| families | array | – | – |
| known_gaps | array | – | Never empty. An empty list would mean 'not checked', not 'no gaps'. |
| status | string | – | – |
No examples provided.
pl_get_document ~302
Fetch the full document (judgment, act text, register extract...) from a source. `document_id` format depends on the source - numeric id (saos), hex doc_id (nsa), ELI (isap), KRS number (krs), signature (kio, uodo)... - see the `document_id` field in pl_list_sources. Long documents are paginated at ~5000 characters per page: response is JSON with `content`, `page`, `total_pages`, `has_more` - iterate `page` while `has_more` (`page` is 1-based, exactly as in pl_search; `page_number` is a deprecated alias kept for backward compatibility, and is echoed in the response for the same reason). Sources that paginate the document themselves (isap) report `pagination: "native"` and carry their own page footer inside `content`. Some sources need `extra` (e.g. eu-compliance: {"regulation": "GDPR"}). Errors: `unknown_source`, `invalid_arg` (missing required extra, page < 1, conflicting page/page_number), `source_unavailable`, `upstream_error` (e.g. connector's not_found - check the identifier or search first).
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | – |
| extra | – | – | – |
| page | integer | – | – |
| page_number | – | – | – |
| source | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pl_list_sources ~182
List available Polish/EU legal data sources, or inspect one source's live tool schemas. Without arguments: full catalog (id, coverage, capabilities, native tool names, and `native_params` - the NATIVE parameter name each unified parameter maps to, e.g. eu-compliance pl_get_document -> {"tool": "eu_article", "document_id": "article_number"}) - reads a local registry, spawns nothing. With `source_id`: connects to that connector (lazy spawn on first use) and returns its live tools/list with input schemas - needed for native tools that the unified tools do not cover. Optional `group` filter: 'pl' or 'eu'. Errors: `unknown_source` (bad source_id), `source_unavailable` (connector could not start).
| Name | Type | Req | Description |
|---|---|---|---|
| group | – | – | – |
| source_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pl_search ~281
Unified search across any registered source (SAOS, NSA, ISAP, EUREKA, KIO, UODO...). Common parameters are translated to the source's native names (dateFrom vs date_from, 0- vs 1-based pages - handled here; `page` is ALWAYS 1-based, and is the same parameter name in pl_get_document). `date_from`/`date_to`: YYYY-MM-DD. `limit`: results per page (clamped to the source maximum). `extra`: source-specific native filters merged verbatim (e.g. {"courtType": "SUPREME"} for saos, {"country": "es"} for legalize - the native names are listed under `native_params` in pl_list_sources). `page_number` is a deprecated alias of `page`; prefer `page`. Errors: `unknown_source`, `invalid_arg` (source has no search tool, e.g. krs; missing required extra; page < 1), `source_unavailable`, `upstream_error` (connector's own error code preserved in message).
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | – | – | – |
| date_to | – | – | – |
| extra | – | – | – |
| limit | – | – | – |
| page | integer | – | – |
| page_number | – | – | – |
| query | – | – | – |
| source | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.matematicsolutions/prawo-pl-mcp server?
io.github.matematicsolutions/prawo-pl-mcp is listed in the public MCP registry as io.github.matematicsolutions/prawo-pl-mcp. One MCP server for Polish legal data - courts, legislation, KRS, tax, KIO, UODO via 4 unified tools. This page covers its PyPI package (prawo-pl-mcp).
Is the io.github.matematicsolutions/prawo-pl-mcp server safe to use?
io.github.matematicsolutions/prawo-pl-mcp scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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/prawo-pl-mcp server expose?
io.github.matematicsolutions/prawo-pl-mcp exposes 5 tools: pl_coverage, pl_list_sources, pl_search, pl_get_document, pl_call. Their descriptions and schemas cost roughly 1,111 tokens of context every time the server is loaded.
Is the io.github.matematicsolutions/prawo-pl-mcp server still maintained?
io.github.matematicsolutions/prawo-pl-mcp is still listed as active in the MCP registry. We last reached this channel on 20 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/prawo-pl-mcp server under?
io.github.matematicsolutions/prawo-pl-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.