Ext Ops Panel
Open dashboard
Comparison

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

Where each is published
Marketplacexmlvalidio.github.imysfylmz/xrechnung-mcp
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

xmlvalid vs io.github.imysfylmz/xrechnung-mcp
Factxmlvalidio.github.imysfylmz/xrechnung-mcp
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (xmlvalid.com/mcp)On your machine (@e-rechnung-inbox/xrechnung-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/imysfylmz/e-rechnung-inbox
Changes in the last 7 days (differs)20
First seen (differs)2026-10-222026-10-11
Endpoint at the last check (differs)not checked yetno 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

In its own words, on Official MCP Registry:

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

io.github.imysfylmz/xrechnung-mcp

In its own words, on Official MCP Registry:

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 Code
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 Code
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.

Where the data comes from: how the catalog is built