VAT White List (Poland)
PYPI · VAT-WHITELIST-MCP
Look up Polish VAT taxpayers by NIP, REGON or bank account and verify account associations.
Available components
Last scanned (6 hours ago)
Scores higher than 80% of PyPI servers
Category Finance and Payments
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
- 1 of 31 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/vat-whitelist-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 304 tokens (~60/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 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 5 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 current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 5 Nov 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.
- 4 Nov 26 −12
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.27 ▲ functional
- Package version: 0.1.0 → 0.1.1 functional
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- 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 6 Nov 2026 · Analysed pypi/vat-whitelist-mcp@0.1.1
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/vat-whitelist-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SmartMobileHouse/vat-whitelist-mcp/.github/workflows/publish.yml@refs/tags/v0.1.1 |
| Rekor log index | 3690048826 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:e528a24591f3688e61f2846f518221fca10fbe45e3172dff5896d2f6f4cab0fa |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| 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 →
check_bank_account ~86
Check account association with an active taxpayer on YYYY-MM-DD. id_type: nip or regon. accountAssigned is the API's TAK/NIE answer; API failures raise errors and must never be interpreted as a negative match.
| Name | Type | Req | Description |
|---|---|---|---|
| bank_account | string | yes | – |
| date | string | yes | – |
| id_type | string | yes | – |
| identifier | string | yes | – |
No output schema declared.
No examples provided.
search_bulk ~90
Look up 1–30 identifiers in one request on YYYY-MM-DD. id_type: nip, regon, or bank_account. Results retain each identifier's subjects or API error. Only successful empty entries appear in unmatched. count is the number of returned entries, not the number of taxpayers.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| id_type | string | yes | – |
| identifiers | array | yes | – |
No output schema declared.
No examples provided.
search_by_bank_account ~45
Find taxpayers for a Polish bank account on YYYY-MM-DD; accepts NRB or PL IBAN.
| Name | Type | Req | Description |
|---|---|---|---|
| bank_account | string | yes | – |
| date | string | yes | – |
No output schema declared.
No examples provided.
search_by_nip ~39
Look up taxpayer details by NIP on an explicit YYYY-MM-DD date.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| nip | string | yes | – |
No output schema declared.
No examples provided.
search_by_regon ~44
Look up taxpayer details by 9- or 14-digit REGON on YYYY-MM-DD.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| regon | string | yes | – |
No output schema declared.
No examples provided.
How do I install the VAT White List (Poland) MCP server?
VAT White List (Poland) runs locally as a PyPI package, launched with uvx vat-whitelist-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 · vat-whitelist-mcp
claude mcp add smartmobilehouse-vat-whitelist-mcp -- uvx vat-whitelist-mcp
What is the VAT White List (Poland) MCP server?
VAT White List (Poland) is an MCP server listed in the public MCP registry as io.github.SmartMobileHouse/vat-whitelist-mcp. Look up Polish VAT taxpayers by NIP, REGON or bank account and verify account associations. This page covers its PyPI package (vat-whitelist-mcp).
Is the VAT White List (Poland) MCP server safe to use?
VAT White List (Poland) scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 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 VAT White List (Poland) MCP server expose?
VAT White List (Poland) exposes 5 tools: search_by_nip, search_by_regon, search_by_bank_account, search_bulk, check_bank_account. Their descriptions and schemas cost roughly 304 tokens of context every time the server is loaded.
Is the VAT White List (Poland) MCP server still maintained?
VAT White List (Poland) is still listed as active in the MCP registry. We last reached this channel on 6 November 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 VAT White List (Poland) MCP server under?
VAT White List (Poland) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the VAT White List (Poland) MCP server?
VerifyMCP ran 16 checks on VAT White List (Poland), covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.