mcpbeat Sign in

ZUGFeRD Validator MCP Server

by zugferd-validator Your server? Claim it
answering

ZUGFeRD Validator is answering right now. Last checked 15 min ago. 84 installs a week from npm. It exposes 5 tools.

Validiert E-Rechnungen (ZUGFeRD/Factur-X, XRechnung) gegen EN 16931 mit Korrekturvorschlägen.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 132 · avg 9 · -51% w/w
a month agotoday
Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
122 ms
Response time
average over 24h
84
Installs / week
npm and PyPI

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 August 2026. No other catalogue keeps this.

28 Aug a tool appeared validation_report
13 Aug a tool changed the parameters it asks for2 times that day create_invoice
and 1 more, back to 13 August 2026

ZUGFeRD Validator missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

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 15 min ago.

run in your terminal
claude mcp add validator --transport http https://api.zugferd-validator.de/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "validator": {
      "url": "https://api.zugferd-validator.de/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.validator]
url = "https://api.zugferd-validator.de/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "validator": {
      "url": "https://api.zugferd-validator.de/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "validator": {
      "url": "https://api.zugferd-validator.de/mcp"
    }
  }
}

This one needs environment variables set before it will start: ZUGFERD_API_KEY (API-Key von https://zugferd-validator.de/konto (Demo-Key: zv_demo_public_zugferd_2026)). The author declared them in the registry entry; get the values from the project itself.

Available tools 5

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

consistency
check_consistency
Prüft ob die sichtbaren PDF-Daten mit den eingebetteten XML-Daten übereinstimmen.
extract
extract_xml
Extrahiert die eingebettete XML-Datei aus einem ZUGFeRD/Factur-X PDF.
invoice
create_invoice
Erstellt aus strukturierten Daten eine valide E-Rechnung — entweder als ZUGFeRD-PDF (PDF/A-3 mit eingebettetem XML) oder als reines XRechnung-XML (mit Leitweg-ID für B2G). Unterstützt mehrere Positionen, alle USt-Kategorien, Rabatte/Zuschläge und Zahlungsangaben. Stateless — es wird nichts gespeichert.
validate
validate_invoice
Validiert eine E-Rechnung (ZUGFeRD/Factur-X PDF oder XRechnung XML) gegen EN 16931 und gibt strukturierte Ergebnisse mit Korrekturvorschlägen zurück.
validation
validation_report
Erzeugt aus einer E-Rechnung einen Validierungsbericht als PDF (PDF/A-3b) zum Ablegen und Weitergeben. Der Bericht nennt Ergebnis, alle Meldungen mit Regel-ID und Feld, den Prüfzeitpunkt, Format und Profil, die SHA-256-Prüfsumme der geprüften Datei sowie die Versionen der Prüfwerkzeuge. Auf Wunsch wird die geprüfte Rechnung sichtbar angehängt. Gibt das PDF base64-kodiert zurück. Ab dem Tarif Automatisieren.

Endpoints

URLTransportStateLatencyChecked
https://api.zugferd-validator.de/mcp streamable-http answering 146 ms 15 min ago

Alternatives to ZUGFeRD Validator

same job, measured the same way
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
C
Einvoicewiz
by einvoicewiz

Generate & validate EN 16931 e-invoices (Factur-X, ZUGFeRD, XRechnung); verification certificates

7 tools answering
Invoicehub
by invoicehub

Validate, generate & convert EU e-invoices (UBL, CII, XRechnung, Factur-X) — EN 16931 pre-validated.

4 tools answering
MCP Einvoicing De
by cmendezs

German e-invoicing MCP server: ZUGFeRD 2.x, XRechnung 3.x, EN 16931, KoSIT validation, Peppol.

309 installs/wk local only
Einvoice
by makririch

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

31 installs/wk local only
Rechnungslotse: deutsche E-Rechnung
by rechnungslotse

XRechnung/ZUGFeRD erstellen, gegen EN 16931 prüfen, Fehler mit Regel-ID erklären. Ohne Konto.

18 tools answering
Xrechnung MCP
by imysfylmz

Validate and parse German e-invoices (XRechnung, ZUGFeRD, Factur-X) offline. No API key.

40 installs/wk local only
InvoiceXML
by invoicexml

Create, validate, convert & extract compliant e-invoices (UBL, Factur-X, ZUGFeRD, XRechnung)

answering

ZUGFeRD Validator — questions

Answers built from our own checks of this server.

What can ZUGFeRD Validator do?
It exposes 5 tools, read directly from the server on our last check. Among them: check_consistency, create_invoice, extract_xml, validate_invoice, validation_report. 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 ZUGFeRD Validator 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 122 ms. The bar chart above shows every period we have measured.
Is ZUGFeRD Validator still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect ZUGFeRD Validator?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does ZUGFeRD Validator need an API key?
No. ZUGFeRD Validator completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is ZUGFeRD Validator?
It answers our handshake in 122 ms on average, which is faster than 81% 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.
How many people use ZUGFeRD Validator?
The npm package zugferd-mcp-client was installed 84 times in the last week. Week over week that is -51%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.