E-Invoice Checker vs ZUGFeRD Validator
E-Invoice Checker is an MCP server published by einvoicechecker.com. Marketplaces we read that list it: 1 (Official MCP Registry). ZUGFeRD Validator is an MCP server published by zugferd-validator.de. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   E-Invoice Checker |  ZUGFeRD Validator |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.2 Downloads/month (npm): 339 Downloads/week (npm): 69 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | E-Invoice Checker | ZUGFeRD Validator |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (einvoicechecker.com/v1/mcp) | Remote server (api.zugferd-validator.de/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/vpukhalskyi/einvoicechecker-mcp | github.com/tzatti1/zugferd-validator |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 13 h ago | Responded 2 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
E-Invoice Checker
Validate, parse and render EU e-invoices: XRechnung, ZUGFeRD, Factur-X, Peppol BIS 3.0, KSeF.
ZUGFeRD Validator
Validiert E-Rechnungen (ZUGFeRD/Factur-X, XRechnung) gegen EN 16931 mit Korrekturvorschlägen.
How to run each
E-Invoice Checker As a remote MCP server
claude mcp add --transport http einvoice https://einvoicechecker.com/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
ZUGFeRD Validator As a remote MCP server
claude mcp add --transport http validator https://api.zugferd-validator.de/mcp --header "X-Api-Key: <YOUR_X_API_KEY>"Requires: ZUGFERD_API_KEY (secret), X-Api-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of E-Invoice Checker publish no settings it asks for, so we do not compare settings.
What it can do: E-Invoice Checker · What it can do: ZUGFeRD Validator · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.