InvoiceIn — examples
[MCP server rated A on Glama]
[Run in Postman]
Any European or UAE (PINT AE) e-invoice a business receives → one canonical EN 16931 JSON, a validation report with plain-language fix hints, a PDF, CSV or DATEV export. One stateless endpoint, nothing stored.
Accepts: XRechnung (UBL and CII), EN 16931 UBL 2.1 Invoice/CreditNote, Peppol BIS Billing 3, CII D16B, ZUGFeRD 1.0 / 2.x and Factur-X hybrid PDFs, Italy's FatturaPA 1.2, Poland's KSeF FA(2)/FA(3), Romania's RO e-Factura (CIUS-RO), the UAE's PINT AE (Billing and Self-Billing).
Validated against: EN 16931 validation artefacts 1.3.17, XRechnung 3.0.2 (KoSIT Schematron 2.6.0), Peppol BIS Billing 3, FNFE CTC-FR 1.4.0.04 (the BR-FR rules; runs when seller and buyer are both established in France), CIUS-RO 1.0.1, OpenPeppol's PINT AE 1.0.4 for the UAE (free check page: https://invoicein.peculiar.systems/uae), the UBL, CII, FatturaPA and KSeF schemas — plus arithmetic cross-checks on every format and market conventions no Schematron reads (German Skonto terms in free text, the Polish KSeF number). The live list with versions is at GET /v1/formats.
This repository holds runnable examples, sample invoices you can test with, and the MCP registry manifest. The service itself is not open source.
Nothing you send is stored: the document is parsed in memory and the response is built from it. Privacy (full policy) · Terms
The bridge in bridge/ is a transparent proxy, not a second implementation: it mirrors whatever tools/list returns from the hosted server, so the two can never drift. The five tools and their annotations — all read-only, non-destructive, idempotent, closed-world — are in bridge/tools.json, checked by tests/. A static analyser reading the bridge source alone sees one dispatch callback and no tools; that is the proxy, not the tool surface.
60 seconds
No key yet? Leave the header out: 5 invoices a day per IP, same output, and every answer says how many are left. A free key — 100 invoices, no card, no expiry — is issued at once, on the product page or with one call:
The response (full example):
When something is wrong, every failed rule carries a hint in the requested language (example, KSeF FA(3) in Polish):
Endpoints
Body: multipart field file, or the raw XML/PDF. Send a real User-Agent (Cloudflare rejects the default Python-urllib one with error 1010). Auth: X-Api-Key or Authorization: Bearer. One invoice = one credit whatever outputs you request; a file that carries several invoices (a FatturaPA lot) costs one per invoice. Remaining credits come back in X-Credits-Remaining.
Examples in this repo
Sample invoices
Both XRechnung files produce the same canonical JSON (only the syntax-specific extensions block differs) — that is the point of the canonical model.
What it does not do
No OCR (a PDF without embedded XML is rejected with pdf-no-xml). Not a Peppol access point, not a French PDP, not a UAE Accredited Service Provider, not a KSeF or SdI client: it reads what you already received and never transmits an invoice anywhere. Factur-X/ZUGFeRD profiles below EN 16931 (MINIMUM, BASIC WL, BASIC) get schema and arithmetic checks only, because the EN 16931 rules would only produce noise there. Validation results are informational, not legal advice.
Licence
The examples in this repository are MIT. Sample invoices keep the licences listed above.