io.github.imysfylmz/xrechnung-mcp
NPM · @E-RECHNUNG-INBOX/XRECHNUNG-MCP
Validate and parse German e-invoices (XRechnung, ZUGFeRD, Factur-X) offline. No API key.
Available components
Last scanned (14 hours ago)
Scores higher than 46% 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 Security88
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects @hono/node-server 2.0.12, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 103 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 72 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 261 tokens (~87/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −5
- Stability: pass → 0.63 functional
- 29 Oct 26 −3
- CVE-2026-118663 affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ security
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
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/@e-rechnung-inbox/xrechnung-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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 103 packages
| Packages resolved | 103 |
|---|---|
| Stale | 30 |
| 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 →
extract_zugferd ~94
Extract the embedded Factur-X XML from a ZUGFeRD PDF. Input is the PDF content as a base64-encoded string. Returns the embedded XML as a UTF-8 string, or an empty string if no XML is found.
| Name | Type | Req | Description |
|---|---|---|---|
| pdfBase64 | string | yes | Base64-encoded ZUGFeRD (Factur-X) PDF bytes. Whitespace in the base64 string is tolerated. |
No output schema declared.
No examples provided.
parse_invoice ~82
Parse an XRechnung or ZUGFeRD/Factur-X XML document into a normalized invoice structure with header, totals, line items, and tax breakdown. Useful for extracting invoice data without the full validation cycle.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | The XRechnung/ZUGFeRD invoice XML. UBL or UN/CEFACT CII flavors both accepted. |
No output schema declared.
No examples provided.
validate_xrechnung ~85
Validate an XRechnung or ZUGFeRD/Factur-X XML document against the EN 16931 core model. Returns a structured report with severity-graded issues. Stateless, offline.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | The XRechnung/ZUGFeRD invoice XML. UBL or UN/CEFACT CII flavors both accepted. Must be a non-empty string. |
No output schema declared.
No examples provided.
How do I install the io.github.imysfylmz/xrechnung-mcp server?
io.github.imysfylmz/xrechnung-mcp runs locally as an npm package, launched with npx -y @e-rechnung-inbox/xrechnung-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 · @e-rechnung-inbox/xrechnung-mcp
claude mcp add imysfylmz-xrechnung-mcp -- npx -y @e-rechnung-inbox/xrechnung-mcp
What is the io.github.imysfylmz/xrechnung-mcp server?
io.github.imysfylmz/xrechnung-mcp is listed in the public MCP registry as io.github.imysfylmz/xrechnung-mcp. Validate and parse German e-invoices (XRechnung, ZUGFeRD, Factur-X) offline. No API key. This page covers its npm package (@e-rechnung-inbox/xrechnung-mcp).
Is the io.github.imysfylmz/xrechnung-mcp server safe to use?
io.github.imysfylmz/xrechnung-mcp scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 io.github.imysfylmz/xrechnung-mcp server expose?
io.github.imysfylmz/xrechnung-mcp exposes 3 tools: validate_xrechnung, parse_invoice, extract_zugferd. Their descriptions and schemas cost roughly 261 tokens of context every time the server is loaded.
Is the io.github.imysfylmz/xrechnung-mcp server still maintained?
io.github.imysfylmz/xrechnung-mcp 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 io.github.imysfylmz/xrechnung-mcp server under?
io.github.imysfylmz/xrechnung-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.imysfylmz/xrechnung-mcp server?
VerifyMCP ran 15 checks on io.github.imysfylmz/xrechnung-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.imysfylmz/xrechnung-mcp: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.