E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) vs XRechnung Validator
E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) is an MCP server published by nyo-agentti. Marketplaces we read that list it: 1 (Official MCP Registry). XRechnung Validator is an MCP server published by wenboteng. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  XRechnung Validator | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 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 validator & repair check (XRechnung, Peppol BIS 3, EN 16931) | XRechnung Validator |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Remote server (einvoice-validator-k2qw.onrender.com/mcp) | On your machine (xrechnung-validator-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/wenboteng/xrechnung-validator |
| Changes in the last 7 days (differs) | 2 | 4 |
| First seen (differs) | 2026-10-24 | 2026-10-19 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
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 validator & repair check (XRechnung, Peppol BIS 3, EN 16931)
Validate XRechnung, Peppol BIS 3 and EN 16931 invoices with KoSIT; explain rules; check auto-repair
XRechnung Validator
Validate XRechnung XML and ZUGFeRD / Factur-X PDFs with the free checkxrechnung.com API.
How to run each
E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) As a remote MCP server
claude mcp add --transport http einvoice-validator https://einvoice-validator-k2qw.onrender.com/mcpXRechnung Validator As a local MCP server: npm package
claude mcp add --transport stdio xrechnung-validator -- npx -y xrechnung-validator-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) · What it can do: XRechnung 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.