ZUGFeRD Validator
NPM · ZUGFERD-MCP-CLIENT · 2 COMPONENTS · SCANNED SEP 25
Validiert E-Rechnungen (ZUGFeRD/Factur-X, XRechnung) gegen EN 16931 mit Korrekturvorschlägen.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 63 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 609 tokens (~152/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the ZUGFeRD Validator MCP server?
ZUGFeRD Validator runs locally as an npm package, launched with npx -y zugferd-mcp-client. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · zugferd-mcp-client
claude mcp add de-zugferd-validator-validator -- npx -y zugferd-mcp-client
{
"mcpServers": {
"de-zugferd-validator-validator": {
"command": "npx",
"args": [
"-y",
"zugferd-mcp-client"
]
}
}
} {
"servers": {
"de-zugferd-validator-validator": {
"command": "npx",
"args": [
"-y",
"zugferd-mcp-client"
]
}
}
} codex mcp add de-zugferd-validator-validator -- npx -y zugferd-mcp-client
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"de-zugferd-validator-validator": {
"type": "local",
"command": [
"npx",
"-y",
"zugferd-mcp-client"
],
"enabled": true
}
}
} openclaw mcp add de-zugferd-validator-validator --command npx --arg -y --arg zugferd-mcp-client
mcp_servers:
de-zugferd-validator-validator:
command: "npx"
args: ["-y", "zugferd-mcp-client"] {
"McpServers": {
"de-zugferd-validator-validator": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"zugferd-mcp-client"
]
}
}
} assistant mcp add de-zugferd-validator-validator -t stdio -c npx -a -y zugferd-mcp-client
{
"mcpServers": {
"de-zugferd-validator-validator": {
"command": "npx",
"args": [
"-y",
"zugferd-mcp-client"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/zugferd-mcp-client@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_consistency ~54
Prüft ob die sichtbaren PDF-Daten mit den eingebetteten XML-Daten übereinstimmen.
| Name | Type | Req | Description |
|---|---|---|---|
| pdf_content | string | yes | Base64-kodierter Inhalt der ZUGFeRD-PDF-Datei |
No output schema declared.
No examples provided.
create_invoice ~387
Erstellt aus strukturierten Daten eine valide E-Rechnung — ZUGFeRD-PDF (PDF/A-3 mit eingebettetem XML) oder reines XRechnung-XML (mit Leitweg-ID für B2G). Mehrere Positionen, alle USt-Kategorien, Rabatte/Zuschläge und Zahlungsangaben. Beträge in Cent. Stateless.
| Name | Type | Req | Description |
|---|---|---|---|
| allowances_charges | array | – | Rabatte/Zuschläge auf Dokumentebene |
| buyer | object | yes | Käufer |
| buyer_reference | string | – | Leitweg-ID / Käuferreferenz (XRechnung Pflicht) |
| currency | string | – | Standard EUR |
| date | string | yes | Belegdatum (YYYY-MM-DD) |
| document_type | string | – | Standard invoice. credit_note=Gutschrift/Storno, corrected=Korrektur, self_billed=Gutschriftverfahren, prepayment=Anzahlung, partial=Teilrechnung |
| due_date | string | – | Fälligkeit (YYYY-MM-DD) |
| format | string | yes | 'zugferd' = PDF, 'xrechnung' = XML |
| lines | array | yes | Rechnungspositionen (mindestens eine) |
| note | string | – | – |
| number | string | yes | Belegnummer |
| payment_means | object | – | – |
| payment_terms | string | – | – |
| preceding_invoice | object | – | Bezug auf Ursprungsrechnung (BT-25/26) bei Storno/Korrektur/Gutschrift |
| self_check | boolean | – | Sofort gegen EN 16931 prüfen (langsamer). Standard false. |
| seller | object | yes | Verkäufer |
| seller_logo | string | – | Logo Base64 (PNG/JPG) — nur Pro/Ultra |
| type_code | string | – | Roher UNTDID-1001-Code (überschreibt document_type) |
No output schema declared.
No examples provided.
extract_xml ~53
Extrahiert die eingebettete XML-Datei aus einem ZUGFeRD/Factur-X PDF.
| Name | Type | Req | Description |
|---|---|---|---|
| pdf_content | string | yes | Base64-kodierter Inhalt der ZUGFeRD-PDF-Datei |
No output schema declared.
No examples provided.
validate_invoice ~115
Validiert eine E-Rechnung (ZUGFeRD/Factur-X PDF oder XRechnung XML) gegen EN 16931 und gibt strukturierte Ergebnisse mit Korrekturvorschlägen zurück.
| Name | Type | Req | Description |
|---|---|---|---|
| file_content | string | yes | Base64-kodierter Inhalt der PDF- oder XML-Datei |
| file_type | string | yes | 'pdf' für ZUGFeRD/Factur-X, 'xml' für XRechnung |
| profile | string | – | Erwartetes Profil (optional, wird automatisch erkannt) |
No output schema declared.
No examples provided.
What is the ZUGFeRD Validator MCP server?
ZUGFeRD Validator is an MCP server listed in the public MCP registry as de.zugferd-validator/validator. Validiert E-Rechnungen (ZUGFeRD/Factur-X, XRechnung) gegen EN 16931 mit Korrekturvorschlägen. This page covers its npm package (zugferd-mcp-client).
Is the ZUGFeRD Validator MCP server safe to use?
ZUGFeRD Validator scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ZUGFeRD Validator MCP server expose?
ZUGFeRD Validator exposes 4 tools: validate_invoice, extract_xml, check_consistency, create_invoice. Their descriptions and schemas cost roughly 609 tokens of context every time the server is loaded.
Is the ZUGFeRD Validator MCP server still maintained?
ZUGFeRD Validator is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ZUGFeRD Validator MCP server under?
ZUGFeRD Validator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.