REGON (Polish business register)
PYPI · REGON-MCP
Look up Polish businesses in the GUS REGON register (BIR1) by NIP, REGON, or KRS.
Available components
Last scanned (16 hours ago)
Scores higher than 94% of PyPI servers
Category CRM and Sales
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 32 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 SmartMobileHouse/regon-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 67 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 507 tokens (~84/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 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 current MCP spec version (2026-07-28).Pass
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.
- 16 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 15 Oct 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.83 functional
- 14 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 13 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 97. That category is still filling its 30-day observation window: 27 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.
- 4 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Oct 26 +16
- Malware scan: unverified → pass ▲ security
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 16 Oct 2026 · Analysed pypi/regon-mcp@0.2.2
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | SmartMobileHouse/regon-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SmartMobileHouse/regon-mcp/.github/workflows/publish.yml@refs/tags/v0.2.2 |
| Rekor log index | 2406648906 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:fee32f4f807ceac0b84641a0ceb083864a1a6a2f70041e7be914eb716d23e446 |
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 32 packages
| Packages resolved | 32 |
|---|---|
| Stale | 1 |
| No linked repository | 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 →
get_full_report ~65
Fetch a detailed REGON report for one entity by REGON. Choose report_type from list_report_types(), based on the entity's `type` and `silo_id` returned by a search.
| Name | Type | Req | Description |
|---|---|---|---|
| regon | string | yes | – |
| report_type | string | yes | – |
No output schema declared.
No examples provided.
list_report_types ~192
List valid report_type values for get_full_report(), with guidance. These are the BIR1.1 report names. Picking the right report: - type "P" (legal person) -> BIR11OsPrawna - type "F" (natural person) -> by silo_id: 1 -> BIR11OsFizycznaDzialalnoscCeidg 2 -> BIR11OsFizycznaDzialalnoscRolnicza 3 -> BIR11OsFizycznaDzialalnoscPozostala 4 -> BIR11OsFizycznaDzialalnoscSkreslonaDo20141108 - local units (LP / LF) -> BIR11JednLokalnaOsPrawnej / ...OsFizycznej
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_bulk ~116
Look up up to 20 entities of the same identifier type in one call. id_type must be one of: "nip", "krs", "regon9", "regon14". The response adds `requested` (normalized inputs) and `unmatched` (requested ids with no returned row) so partial results are explicit. For KRS the service does not echo the KRS in search rows, so `unmatched` is null there.
| Name | Type | Req | Description |
|---|---|---|---|
| id_type | string | yes | – |
| identifiers | array | yes | – |
No output schema declared.
No examples provided.
search_by_krs ~34
Look up a Polish business entity by KRS (10-digit court-register number).
| Name | Type | Req | Description |
|---|---|---|---|
| krs | string | yes | – |
No output schema declared.
No examples provided.
search_by_nip ~63
Look up a Polish business entity by NIP (10-digit tax id). Returns basic registry data (name, REGON, address, entity type). Use the returned REGON with get_full_report() for the detailed record.
| Name | Type | Req | Description |
|---|---|---|---|
| nip | string | yes | – |
No output schema declared.
No examples provided.
search_by_regon ~37
Look up a Polish business entity by REGON (9- or 14-digit statistical id).
| Name | Type | Req | Description |
|---|---|---|---|
| regon | string | yes | – |
No output schema declared.
No examples provided.
How do I install the REGON (Polish business register) MCP server?
REGON (Polish business register) runs locally as a PyPI package, launched with uvx regon-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 · regon-mcp
claude mcp add smartmobilehouse-regon-mcp -- uvx regon-mcp
What is the REGON (Polish business register) MCP server?
REGON (Polish business register) is an MCP server listed in the public MCP registry as io.github.SmartMobileHouse/regon-mcp. Look up Polish businesses in the GUS REGON register (BIR1) by NIP, REGON, or KRS. This page covers its PyPI package (regon-mcp).
Is the REGON (Polish business register) MCP server safe to use?
REGON (Polish business register) scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. 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 REGON (Polish business register) MCP server expose?
REGON (Polish business register) exposes 6 tools: search_by_nip, search_by_regon, search_by_krs, search_bulk, get_full_report, list_report_types. Their descriptions and schemas cost roughly 507 tokens of context every time the server is loaded.
Is the REGON (Polish business register) MCP server still maintained?
REGON (Polish business register) is still listed as active in the MCP registry. We last reached this channel on 16 October 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 REGON (Polish business register) MCP server under?
REGON (Polish business register) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.