finisma – ZUGFeRD e-invoices vs ValidateFin
finisma – ZUGFeRD e-invoices is an MCP server published by finisma.de. Marketplaces we read that list it: 1 (Official MCP Registry). ValidateFin is an MCP server published by elnicaise. 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 |  ValidateFin | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 No figure published Not marked · First seen |
Listed Version: 1.2.1 Downloads/month (npm): 363 Downloads/week (npm): 89 Forks (GitHub): 0 Stars (GitHub): 1 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 | finisma – ZUGFeRD e-invoices | ValidateFin |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | Remote server (finisma.de/api/mcp) | On your machine (@validatefin/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/elnicaise/validatefin-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago | 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
finisma – ZUGFeRD e-invoices
Create ZUGFeRD e-invoices from JSON or PDF, verify Factur-X, check VAT IDs and Peppol.
ValidateFin
Validate SEPA, UBL/Peppol, XRechnung, camt, ACH & IBAN files locally — no data leaves your machine.
How to run each
finisma – ZUGFeRD e-invoices As a remote MCP server
claude mcp add --transport http finisma https://finisma.de/api/mcpValidateFin As a local MCP server: npm package
claude mcp add --transport stdio validatefin -- npx -y @validatefin/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only finisma – ZUGFeRD e-invoices has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of ValidateFin nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: finisma – ZUGFeRD e-invoices · What it can do: ValidateFin · 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.