Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Veriport: EU VAT number, IBAN, VAT rates and e-invoice checks

NPM · @VERIPORT/MCP

EU VAT numbers on VIES, IBANs, French companies, Peppol IDs, EU VAT rates and e-invoice validation.

Available components

+3 this week 72 Trust /100

Last scanned (21 hours ago)

Scores higher than 44% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1186 tokens (~197/item across 6 items; 6 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 Management30
  • Stability observed for 9 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

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 →

Changelog

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.

  • 21 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.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 53

    First indexed and scored.

Diagnostics

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 Nov 2026 · Analysed npm/@veriport/mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,075 tokens

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 →

Tool Tokens
french_company ~165

Reads a French company from the official registries (the open Recherche d'entreprises API, INSEE Sirene as a fallback): legal name, legal form, NAF activity, status (active or ceased) and dates, head-office address, the establishment asked for when a SIRET is given, and the intra-community VAT number computed from the SIREN with the numbers VIES confirms. Give a SIREN (9 digits) or a SIRET (14 digits), spaces allowed. A ceased company is an answer, not an error. 1 call.

NameTypeReqDescription
idstringyesA SIREN (9 digits) or SIRET (14 digits), e.g. "356000000" or "356 000 000 00048".

No output schema declared.

No examples provided.

peppol_participant ~204

Looks a company up on the Peppol network the way an access point does before it sends: whether its identifier is registered (Peppol SML), which documents it receives (its SMP: Peppol BIS Billing 3.0 invoices and credit notes, and others) and its registered name when its provider published one (Peppol Directory). Give a participant identifier (ICD:value, e.g. "0208:0202239951" or "9930:de136695976") or a Belgian enterprise or VAT number in any form ("BE 0202.239.951"), which is looked up under both 0208 and 9925. receives.invoice / receives.creditNote answer the sender's question. « Not registered » is an answer. 1 call; nothing is sent on the network.

NameTypeReqDescription
idstringyesA Peppol participant identifier (ICD:value) or a Belgian enterprise or VAT number.

No output schema declared.

No examples provided.

validate_einvoice ~264

Checks an e-invoice (XRechnung 3.0 UBL or CII, Peppol BIS Billing 3.0, EN 16931 / Factur-X / ZUGFeRD CII, or a ZUGFeRD / Factur-X hybrid PDF) with the XML schema and the official schematron of its profile: CEN EN 16931 1.3.16, XRechnung 3.0.2, Peppol BIS 3.0.21. Returns valid, the profile and syntax, the errors and warnings with the published rule ids (BR-*, BR-DE-*, PEPPOL-*) and their XPath. Give the XML as text in `xml`, or a PDF as base64 in `pdf_base64`. 5 calls per check (4 a day without a key). Does not send the invoice anywhere and does not store it; not tax advice.

NameTypeReqDescription
pdf_base64string–A ZUGFeRD / Factur-X hybrid PDF, base64-encoded (the embedded XML is checked).
xmlstring–The e-invoice XML as text (UBL 2.1 Invoice or CreditNote, UN/CEFACT CII D16B).

No output schema declared.

No examples provided.

validate_iban ~106

Checks an IBAN the way a payment system does: characters, country, the length the ISO 13616 registry sets, the mod 97-10 check digits, the national BBAN structure. Returns the five checks, the failed rules, the bank and branch identifiers where the registry defines them, and whether the country is in the SEPA schemes. It does not say whether the account exists or who owns it.

NameTypeReqDescription
ibanstringyesThe IBAN, spaces allowed.

No output schema declared.

No examples provided.

validate_vat ~212

Checks the structure and the national check digit, then asks the European Commission’s VIES whether the number is registered for intra-EU trade. Returns valid, the registered name and address where published, the date, and the provenance (source.kind: live, cache or structure_only; source.stale true when the member state did not answer and a dated cached answer was served). With requester (your own VAT number) and a paid key, returns the VIES consultation number. Greece is EL, Northern Ireland XI; GB is not in VIES.

NameTypeReqDescription
countrystring–Two-letter member-state code when the number has no prefix.
numberstringyesThe VAT number, with or without the two-letter prefix, spaces or dots allowed (e.g. "DE136695976").
recordboolean–Keep this validation as a stored record on the account (paid tiers).
requesterstring–Your own EU VAT number, to obtain a VIES consultation number (paid tiers).

No output schema declared.

No examples provided.

vat_rate ~124

The standard, reduced, super-reduced and parking VAT rates of one EU member state, the rate for seven usual categories (digital services, e-books, printed books, foodstuffs, hotel accommodation, restaurant, newspapers), the day the row was verified and the official sources it was read from. Without a country, the rate of one category across the 27 states.

NameTypeReqDescription
categorystring–With no country: one category for every member state.
countrystring–Two-letter member-state code (Greece is EL). Omit to get every state.

No output schema declared.

No examples provided.

Install

How do I install the Veriport: EU VAT number, IBAN, VAT rates and e-invoice… MCP server?

Veriport: EU VAT number, IBAN, VAT rates and e-invoice… runs locally as an npm package, launched with npx -y @veriport/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @veriport/mcp

# add to Claude Code
claude mcp add io-veriport-veriport -- npx -y @veriport/mcp
Common questions

What is the Veriport: EU VAT number, IBAN, VAT rates and e-invoice… MCP server?

Veriport: EU VAT number, IBAN, VAT rates and e-invoice… is an MCP server listed in the public MCP registry as io.veriport/veriport. EU VAT numbers on VIES, IBANs, French companies, Peppol IDs, EU VAT rates and e-invoice validation. This page covers its npm package (@veriport/mcp).

Is the Veriport: EU VAT number, IBAN, VAT rates and e-invoice… MCP server safe to use?

Veriport: EU VAT number, IBAN, VAT rates and e-invoice… scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Veriport: EU VAT number, IBAN, VAT rates and e-invoice… MCP server expose?

Veriport: EU VAT number, IBAN, VAT rates and e-invoice… exposes 6 tools: validate_vat, validate_iban, vat_rate, validate_einvoice, french_company, peppol_participant. Their descriptions and schemas cost roughly 1,075 tokens of context every time the server is loaded.

Is the Veriport: EU VAT number, IBAN, VAT rates and e-invoice… MCP server still maintained?

Veriport: EU VAT number, IBAN, VAT rates and e-invoice… is still listed as active in the MCP registry. We last reached this channel on 21 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 Veriport: EU VAT number, IBAN, VAT rates and e-invoice… MCP server under?

Veriport: EU VAT number, IBAN, VAT rates and e-invoice… 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 Veriport: EU VAT number, IBAN, VAT rates and e-invoice… MCP server?

VerifyMCP ran 16 checks on Veriport: EU VAT number, IBAN, VAT rates and e-invoice…, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.