mcpbeat Sign in

E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) MCP Server

by nyo-agentti Your server? Claim it
answering

E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) is answering right now. Last checked 14 min ago. It exposes 2 tools.

Validate XRechnung, Peppol BIS 3 and EN 16931 invoices with KoSIT; explain rules; check auto-repair

Uptime history 26 hours of history
26 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
126 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add einvoice-validator --transport http https://einvoice-validator-k2qw.onrender.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://einvoice-validator-k2qw.onrender.com/mcp
~/.codex/config.toml
[mcp_servers.einvoice-validator]
url = "https://einvoice-validator-k2qw.onrender.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "einvoice-validator": {
      "url": "https://einvoice-validator-k2qw.onrender.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "einvoice-validator": {
      "type": "http",
      "url": "https://einvoice-validator-k2qw.onrender.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

explain
explain_rule
Explain an EN 16931 / XRechnung / Peppol business rule by id (e.g. BR-CO-10, BR-DE-15, PEPPOL-EN16931-R001): what it means and how to fix it.
validate
validate_einvoice
Validate an XRechnung / Peppol BIS 3 / EN 16931 e-invoice (UBL 2.1 Invoice/CreditNote or CII CrossIndustryInvoice XML) with the official KoSIT validator. Returns accepted/rejected, the matched scenario and every error and warning with rule id, message, location and a link to a plain-language explanation. For rejected files it also reports which errors an automatic repair removes (measured on this file).

Endpoints

URLTransportStateLatencyChecked
https://einvoice-validator-k2qw.onrender.com/mcp streamable-http answering 135 ms 14 min ago

Alternatives to E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931)

same job, measured the same way
xmlvalid
by xmlvalid

Validate XML and e-invoices (XSD, DTD, RelaxNG, EN 16931, Peppol, XRechnung), explain errors

5 tools answering
E-Invoice Checker
by einvoicechecker

Validate, parse and render EU e-invoices: XRechnung, ZUGFeRD, Factur-X, Peppol BIS 3.0, KSeF.

8 tools answering
Eleata e-Invoice Validator
by hernaninverso

Validate EU e-invoices (Peppol, XRechnung, Factur-X, UBL, CII) and explain error codes.

20 installs/wk local only
InvoiceForge
by agenttoolworks

Generate, validate and read EN 16931 and Peppol BIS 3.0 e-invoices, in UBL and CII.

5 tools answering
Invoiceer e-invoicing tools
by invoiceer

Create and validate XRechnung, ZUGFeRD and Peppol e-invoices (KoSIT); Peppol lookup, rule help.

6 tools answering
Attestwire
by attestwire

EN 16931: validate invoice data, UBL/CII or PDF; emit XRechnung/Peppol XML, never a PDF.

25 installs/wk 14 tools answering
Fakturai — German E-Invoice (ZUGFeRD / Factur-X / E-Rechnung)
by fakturai

KoSIT-verified German e-invoices: generate & validate ZUGFeRD, Factur-X, XRechnung, EN 16931.

3 tools answering
Einvoice
by makririch

XRechnung & ZUGFeRD: create, validate, and convert German e-invoices. EN 16931 compliant.

17 installs/wk local only

E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) — questions

Answers built from our own checks of this server.

What can E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) do?
It exposes 2 tools, read directly from the server on our last check. Among them: explain_rule, validate_einvoice. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 126 ms. The bar chart above shows every period we have measured.
How do I connect E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931)?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) need an API key?
No. E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931)?
It answers our handshake in 126 ms on average, which is faster than 93% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.