REGON (Polish business register)
PYPI · REGON-MCP · SCANNED AUG 19
Look up Polish businesses in the GUS REGON register (BIR1) by NIP, REGON, or KRS.
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 →
Supply Chain Security99
- 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 native-build step with no shell scripting around it. View diagnostics → Pass
- 3 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 8 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 Management30
- Stability observed for 9 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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
pypi · regon-mcp
claude mcp add smartmobilehouse-regon-mcp -- uvx regon-mcp
codex mcp add smartmobilehouse-regon-mcp -- uvx regon-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"smartmobilehouse-regon-mcp": {
"type": "local",
"command": [
"uvx",
"regon-mcp"
],
"enabled": true
}
}
} openclaw mcp add smartmobilehouse-regon-mcp --command uvx --arg regon-mcp
mcp_servers:
smartmobilehouse-regon-mcp:
command: "uvx"
args: ["regon-mcp"] {
"mcpServers": {
"smartmobilehouse-regon-mcp": {
"command": "uvx",
"args": [
"regon-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.
- 19 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 13 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Aug 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- 11 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 61
First indexed and scored.
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 19 Aug 2026 · Analysed pypi/regon-mcp@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Dependencies 34 packages
| Packages resolved | 34 |
|---|---|
| Stale | 2 |
| No linked repository | 1 |
| Tree resolution | Complete |
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.
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.