Skip to main content
Glama

EU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions)

Server Details

EN 16931/XRechnung e-invoice validate+create, Peppol routing, EU VAT/EORI, sanctions, KYB. Free tier

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
wsystemdev/eu-business-data-mcp
GitHub Stars
0
Server Listing
EU Business Data MCP
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 14 tools

Disambiguation3/5

The invoice lifecycle tools (create/parse/validate/send) are cleanly separated, but the business-verification surface has real overlap: kyb_check and due_diligence_report both run VIES + register + sanctions and both return a pass/review/fail verdict, so an agent can easily pick the wrong one. einvoice_route also re-runs VIES and Peppol checks that overlap with both, and send_einvoice_sandbox subsumes create_einvoice plus validate_einvoice plus checks, making boundaries fuzzy despite helpful descriptions.

Naming Consistency4/5

All names are snake_case and mostly verb_noun (verify_vat, create_einvoice, screen_sanctions, validate_einvoice, send_einvoice_sandbox), with batch variants predictably suffixed (_batch). Minor deviations are noun-first names like kyb_check, einvoice_route and due_diligence_report, which break the verb-first pattern but remain readable.

Tool Count5/5

14 tools is squarely in the well-scoped range for a domain spanning VAT/EORI validation, company registers, sanctions, and invoice creation/parsing/validation/sending. Each tool has a plausible job, with batch variants justified by rate-limit constraints rather than padding.

Completeness4/5

Coverage is broad: validation primitives, batch variants, composite due-diligence, register lookup, sanctions, and the full create/parse/validate/send invoice path. Gaps are minor but real—no live Peppol send tool (only a REST endpoint reference), no credit-note/PDF output tool, Peppol-specific and French PPF directory rules explicitly not yet supported—workable around but not fully closed.

Available Tools

14 tools
check_fr_pa_registryIs it a French approved e-invoicing platform (PA)?A
Read-onlyIdempotent
Inspect

Is this e-invoicing platform on France's official list of Plateformes Agréées (PA)? name = platform or company name (e.g. 'Pennylane'), website = its site (e.g. 'https://www.acubeapi.com/'); give at least one. Checks the DGFiP lists on impots.gouv.fr: registered PAs (with registration date) and operators awaiting interoperability tests. Returns on_official_list, status (approved | awaiting_interop_tests | possible_match | not_found), scored matches, list date and the official source. Use for supplier due diligence before the French reform (receive from 1 Sep 2026, SMEs issue from 1 Sep 2027). A 'solution compatible' is not a PA itself. Unofficial copy; the official lists prevail.

Inputs: name, limit, website.

create_einvoiceCreate a validated e-invoice (UBL 2.1)A
Read-onlyIdempotent
Inspect

Create a validated EU e-invoice (UBL 2.1) from simple JSON. invoice = {format: en16931|xrechnung|peppol-bis3, invoice_number, issue_date (YYYY-MM-DD), due_date?, tax_point_date?, delivery_date?, currency (EUR), buyer_reference?, seller: {name, vat_id, street, city, postal_code, country, email, phone, contact_name, company_id?, company_id_scheme?, legal_form?}, buyer: {...}, lines: [{description, quantity, unit_price, unit?, vat_category (S|Z|E|AE|K|G|O), vat_rate}], payment: {iban, bic?, terms?}}. Totals and VAT breakdown are computed; returns {valid, xml, totals, errors, fixes}. autofix=true applies the safe fixes (date formats, codes, VAT ID format, misnamed fields) first and returns the corrected input in autofix.invoice.

Inputs: invoice (required), autofix.

due_diligence_reportCounterparty due-diligence reportA
Read-onlyIdempotent
Inspect

Counterparty due-diligence report in one call: VIES VAT, official business register, EU/UN/OFAC/UK sanctions, EC EORI, GLEIF LEI and Peppol e-invoice route, with deterministic risk flags, 0-100 risk score, pass/review/fail verdict, sources and UTC timestamp. company: VAT ID (best), registry number or name; country: ISO code for names.

Inputs: company (required), country.

einvoice_routeCan this company receive e-invoices? (Peppol + mandate)A
Read-onlyIdempotent
Inspect

'Can I e-invoice this company?' id = EU VAT number (e.g. 'BE0403170701') or Peppol id ('0208:0403170701'). Returns VIES VAT status, Peppol registration (Peppol Directory, then SML/SMP; BIS 3 invoice support), the country's B2B e-invoice mandate (dates, format, source) and the recommended format for create_einvoice. France's PPF directory is not included yet.

Inputs: id (required).

kyb_checkKYB check: VAT, register and sanctionsA
Read-onlyIdempotent
Inspect

One-call KYB check of a supplier/customer: EU VAT validation (VIES) + official business register

  • EU/UN/OFAC/UK sanctions screening, returning a pass / review / fail verdict with reasons. company: a VAT ID ('FR40303265045'), a company name, or a registry id; country: optional ISO code (e.g. 'NO').

Inputs: company (required), country, requester.

lookup_companyLook up a company in EU business registersA
Read-onlyIdempotent
Inspect

Look up a company in official European business registers by name or registry number. country: FR (SIREN), NO (org.nr), FI (Y-tunnus), CZ (ICO), PL (KRS number), EE, SK (ICO or name), or any other ISO code / 'LEI' (GLEIF). Name searches return the exact legal entity first (before branches and similar names). Returns legal name, ID, status/active, address, VAT ID, activity code and official source link. Use to confirm a company exists and is active, find its registry number, or map a name to a VAT ID. Free: basic company search costs 0 units and does not use the free tool-call allowance; it is only rate-limited.

Inputs: query (required), limit, country.

parse_einvoiceRead a received e-invoice into JSONA
Read-onlyIdempotent
Inspect

Read an incoming EU e-invoice into one JSON shape: seller, buyer, dates, references, totals, VAT breakdown, payment/IBAN, lines and attachments. Accepts UBL 2.1 Invoice/CreditNote or UN/CEFACT CII XML (XRechnung, Peppol BIS 3, Factur-X XML) in xml, or a ZUGFeRD/Factur-X PDF as base64 in pdf_base64. Use when asked to read, extract or book a received e-invoice. Values are returned as written in the invoice; this does NOT validate it (use validate_einvoice for that).

Inputs: xml, pdf_base64.

screen_sanctionsScreen a name against EU/UN/OFAC/UK sanctionsA
Read-onlyIdempotent
Inspect

Screen a person or company name against official EU, UN, OFAC SDN and UK sanctions lists. Fuzzy matching with transliteration; returns candidate matches with 0-100 scores, list, programme, DOB. A potential match needs human review; this is a screening aid, not legal advice.

Inputs: name (required), country, threshold, birth_year.

send_einvoice_sandboxPreflight and sandbox-send an e-invoiceAInspect

SANDBOX ONLY - never reaches a real buyer. Safe send: first checks the buyer VAT in VIES, whether the buyer can be reached on Peppol, and the buyer name against EU/UN/OFAC/UK sanctions lists, then creates + validates the EN 16931 invoice (same JSON as create_einvoice), and returns one preflight verdict: ok, warn or block, with a plain-English message per check and, for each invoice error, what is wrong, which field and how to fix it. A block (invalid VAT, close sanctions match, invoice errors) stops the send. Otherwise it routes, hands off to the transport and returns an Ed25519-signed evidence receipt (JWS). preflight_only=true: run only the checks and return the verdict, send nothing (use before every send). checks: subset of ["vat","peppol","sanctions"] (default all; validation always runs). transport: "mock" (simulated, default), "recommand" or "e-invoice-be" (the UBL is really submitted to that Peppol access point's sandbox, addressed to W System's own sandbox company). Use it to build and test an integration; real Peppol sending is the REST API POST /einvoice/send with mode=live, after a Peppol mandate and KYC review. autofix=true (only with preflight_only=true): run the checks on a copy with the safe fixes applied and return it in autofix.invoice; review it, then send that corrected invoice. A send never changes the invoice.

Inputs: invoice (required), checks, autofix, transport, +1 more.

validate_einvoiceValidate an e-invoice (EN 16931, XRechnung, Peppol BIS)A
Read-onlyIdempotent
Inspect

Validate an EU e-invoice XML (UBL 2.1 Invoice/CreditNote or UN/CEFACT CII, e.g. XRechnung, Factur-X/ZUGFeRD XML) against the official CEN EN 16931 rules and, for XRechnung, the KoSIT XRechnung 3.0 rules. Returns valid, and every error with its rule ID (e.g. BR-CO-10), a plain-English message, XPath and a fix hint. rules: auto | en16931 | xrechnung. Slovak sellers also get eFaktúra field checks (FR SR transposition v1.13, warnings with ruleset SK-FS); Norwegian sellers get NO-LAW field checks. Peppol-specific rules are not checked yet. For PDFs use the REST endpoint POST /einvoice/validate. fixes lists concrete fixes for the errors (path, current, suggested, explanation, apply safe|amounts|manual). autofix=true applies the safe ones to a copy and returns it in autofix.xml with its new result (the original is unchanged); allow_amount_changes=true also applies total fixes that change the amount due (reported).

Inputs: xml (required), rules, autofix, allow_amount_changes.

verify_batchVerify up to 100 EU VAT numbersA
Read-onlyIdempotent
Inspect

Validate up to 100 EU VAT numbers in one call via VIES (supplier/customer list cleanup, onboarding, invoice runs). Same per-item result as verify_vat; items with member_state_unavailable should be retried later (GB items stay member_state_unavailable until HMRC live access is granted; they are not charged).

Inputs: vats (required), requester. Returns: result

verify_eoriVerify EU EORI number (EC EOS)A
Read-onlyIdempotent
Inspect

Validate an EU EORI (customs Economic Operators Registration and Identification) number, e.g. 'SE5560360793', 'DE1234567890123', against the official European Commission EOS service. Use for import/export, customs declarations and freight-forwarder onboarding. Returns valid/invalid and trader name/address only when the trader consented to publication. UK (GB) EORIs are not in EOS (HMRC checks those); XI EORIs are.

Inputs: eori (required).

verify_eori_batchVerify up to 100 EU EORI numbersA
Read-onlyIdempotent
Inspect

Validate up to 100 EU EORI numbers in one call via the official EC EOS service (customs / import-export KYB).

Inputs: eoris (required). Returns: result

verify_vatVerify EU VAT number (VIES)A
Read-onlyIdempotent
Inspect

Validate an EU VAT number against the official European Commission VIES service (27 EU states + XI Northern Ireland). Use when asked whether a VAT ID is valid/active, before zero-rated reverse-charge B2B invoices, or to get a company's registered name/address from its VAT number. Input: VAT with country prefix, e.g. 'IE6388047V', 'DE811193231' (spaces/dots ok). Returns status: valid | invalid | invalid_format | member_state_unavailable (VIES/member state down - retry later, valid=null) | error, plus name, address (if the member state discloses them; DE/ES often don't) and consultation_number (audit proof) when requester is set. UK (GB) VAT checks are coming soon: until HMRC live access is granted, GB numbers return status member_state_unavailable, valid=null, error HMRC_LIVE_ACCESS_PENDING (not charged). For >1 number use verify_batch.

Inputs: vat (required), requester.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      EU e-invoice validation, as a developer API. Check whether an electronic invoice conforms to EN 16931 — the European standard behind France, Germany, Belgium, Poland and the 2030 ViDA mandate — with a single REST call. Structured JSON errors mapped to the official BR-* business rules. No enterprise sales call required.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Validates EU electronic invoices (Peppol, XRechnung, FatturaPA, etc.) and explains validation error codes, enabling AI coding agents to check invoice validity and get fixes before rejection.
      3
      46 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Create and check EU e-invoices (XRechnung, ZUGFeRD / Factur-X PDF, Peppol BIS, UBL, CII) on your own machine. Validation runs the official KoSIT, CEN and Peppol rules, and its verdicts match the official KoSIT validator 100% on the official test invoices. Free, open source, no API key.
      6
      7
      587 npm
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Designed for AI assistants and agents, this server enables interaction with the EU E-Invoice API functionality. It allows for the validation, parsing, and generation of various international standards like Peppol and XRechnung.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.