xmlvalid vs io.github.imysfylmz/xrechnung-mcp
xmlvalid is an MCP server published by xmlvalid.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.imysfylmz/xrechnung-mcp is an MCP server published by imysfylmz. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.1.1 Downloads/month (npm): 173 Downloads/week (npm): 37 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 | xmlvalid | io.github.imysfylmz/xrechnung-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (xmlvalid.com/mcp) | On your machine (@e-rechnung-inbox/xrechnung-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/imysfylmz/e-rechnung-inbox |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-22 | 2026-10-11 |
| 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
xmlvalid
Validate XML and e-invoices (XSD, DTD, RelaxNG, EN 16931, Peppol, XRechnung), explain errors
io.github.imysfylmz/xrechnung-mcp
Validate and parse German e-invoices (XRechnung, ZUGFeRD, Factur-X) offline. No API key.
How to run each
xmlvalid As a remote MCP server
claude mcp add --transport http xmlvalid https://xmlvalid.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
Requires: Authorization header
io.github.imysfylmz/xrechnung-mcp As a local MCP server: npm package
claude mcp add --transport stdio xrechnung-mcp -- npx -y @e-rechnung-inbox/xrechnung-mcp
Commands 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: xmlvalid · What it can do: io.github.imysfylmz/xrechnung-mcp · 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.