E-RechnungDigital
NPM · ERECHNUNG-DIGITAL-MCP
XRechnung und ZUGFeRD lokal erstellen, lesen und prüfen. Fehlercodes wie BR-DE-15 erklärt.
Available components
Last scanned (12 hours ago)
Scores higher than 35% of npm servers
Category Finance and Payments
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
- 34 of 113 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. 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 10 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 992 tokens (~165/item across 6 items; 6 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 63
First indexed and scored.
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 5 Nov 2026 · Analysed npm/erechnung-digital-mcp@0.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 113 packages
| Packages resolved | 113 |
|---|---|
| Stale | 34 |
| 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_invoice E-Rechnung prüfen ~83
Prüft eine vorhandene E-Rechnung (XML oder ZUGFeRD-PDF) auf Pflichtangaben, Rechenfehler und EN-16931-Regeln. Ersetzt nicht den offiziellen KoSIT-Validator, findet aber die häufigsten Ablehnungsgründe.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Pfad zur .xml- oder .pdf-Datei |
No output schema declared.
No examples provided.
create_invoice E-Rechnung erstellen ~301
Erstellt eine E-Rechnung: XRechnung 3.0 (CII-XML) und ZUGFeRD-PDF mit eingebettetem XML. Prüft vorher alle Pflichtangaben und liefert bei Lücken eine Liste mit Erklärlinks. Ohne seller wird das gespeicherte Absenderprofil genutzt, ohne invoiceNumber die nächste Nummer.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | object | yes | – |
| buyerReference | string | yes | Käuferreferenz: Leitweg-ID bei Behörden, sonst Bestell- oder Projektnummer (BR-DE-15) |
| deliveryDate | string | – | Leistungsdatum, Standard Rechnungsdatum |
| dueDate | string | – | Fälligkeit, Standard Rechnungsdatum plus Zahlungsziel |
| invoiceNumber | string | – | Rechnungsnummer. Leer lassen, um die nächste Nummer aus dem gespeicherten Profil zu nehmen. |
| issueDate | string | – | Rechnungsdatum, Standard heute |
| lines | array | yes | – |
| outputDir | string | – | Zielordner, Standard /tmp/E-Rechnungen |
| paymentTerms | string | – | z. B. 14 Tage netto |
| precedingInvoiceDate | string | – | Datum als JJJJ-MM-TT |
| precedingInvoiceNumber | string | – | Nur bei Korrekturen: Nummer der Ursprungsrechnung |
| seller | object | – | Absender. Weglassen, um das gespeicherte Profil zu nutzen. |
| type | string | – | – |
No output schema declared.
No examples provided.
explain_rule Prüfregel erklären ~66
Erklärt eine Validierungsregel der E-Rechnung (z. B. BR-DE-15, BR-CO-10) in einfachem Deutsch: Bedeutung, Ursache, Lösung und Link.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Regel-ID, z. B. BR-DE-15 |
No output schema declared.
No examples provided.
get_seller_profile Absenderprofil lesen ~50
Liest die gespeicherten Absenderdaten (eigene Firma, Anschrift, Steuer, IBAN) und die letzte Rechnungsnummer. Gibt einen Hinweis zurück, wenn noch nichts gespeichert ist.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_invoice E-Rechnung lesen ~70
Liest eine XRechnung (CII-XML) oder ZUGFeRD-/Factur-X-PDF von der Festplatte und gibt Absender, Empfänger, Positionen und Summen als JSON zurück.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Pfad zur .xml- oder .pdf-Datei |
No output schema declared.
No examples provided.
save_seller_profile Absenderprofil speichern ~279
Speichert die eigenen Firmendaten lokal (/tmp/.erechnung-digital/profile.json), damit künftige Rechnungen nur noch Kunde und Positionen brauchen.
| Name | Type | Req | Description |
|---|---|---|---|
| accountHolder | string | – | – |
| bic | string | – | – |
| city | string | yes | – |
| contactName | string | – | Ansprechpartner (Person oder Abteilung), Pflicht für XRechnung (BR-DE-5) |
| country | string | – | ISO-Ländercode, Standard DE |
| defaultPaymentDays | integer | – | Zahlungsziel in Tagen |
| defaultTaxCase | string | – | Steuerfall, der für neue Positionen gilt |
| string | yes | E-Mail für Rückfragen zur Rechnung | |
| iban | string | yes | – |
| lastInvoiceNumber | string | – | Zuletzt vergebene Rechnungsnummer |
| name | string | yes | Firmenname oder Name der Einzelunternehmerin / des Einzelunternehmers |
| phone | string | – | Telefon, Pflicht für XRechnung (BR-DE-6) |
| postalCode | string | yes | PLZ |
| street | string | yes | Straße und Hausnummer |
| taxNumber | string | – | Steuernummer vom Finanzamt, falls keine USt-IdNr. |
| vatId | string | – | USt-IdNr., z. B. DE123456789 |
No output schema declared.
No examples provided.
How do I install the E-RechnungDigital MCP server?
E-RechnungDigital runs locally as an npm package, launched with npx -y erechnung-digital-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · erechnung-digital-mcp
claude mcp add com-erechnungdigital-mcp -- npx -y erechnung-digital-mcp
What is the E-RechnungDigital MCP server?
E-RechnungDigital is an MCP server listed in the public MCP registry as com.erechnungdigital/mcp. XRechnung und ZUGFeRD lokal erstellen, lesen und prüfen. Fehlercodes wie BR-DE-15 erklärt. This page covers its npm package (erechnung-digital-mcp).
Is the E-RechnungDigital MCP server safe to use?
E-RechnungDigital scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 E-RechnungDigital MCP server expose?
E-RechnungDigital exposes 6 tools: get_seller_profile, save_seller_profile, create_invoice, read_invoice, check_invoice, explain_rule. Their descriptions and schemas cost roughly 849 tokens of context every time the server is loaded.
Is the E-RechnungDigital MCP server still maintained?
E-RechnungDigital is still listed as active in the MCP registry. We last reached this channel on 5 November 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 E-RechnungDigital MCP server under?
E-RechnungDigital declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.