io.github.imysfylmz/xrechnung-mcp
NPM · @E-RECHNUNG-INBOX/XRECHNUNG-MCP · SCANNED SEP 20
Validate and parse German e-invoices (XRechnung, ZUGFeRD, Factur-X) offline. No API key.
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 106 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 26 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 Management90
- Stability observed for 27 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
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
{
"mcpServers": {
"imysfylmz-xrechnung-mcp": {
"command": "npx",
"args": [
"-y",
"@e-rechnung-inbox/xrechnung-mcp"
]
}
}
} {
"servers": {
"imysfylmz-xrechnung-mcp": {
"command": "npx",
"args": [
"-y",
"@e-rechnung-inbox/xrechnung-mcp"
]
}
}
} codex mcp add imysfylmz-xrechnung-mcp -- npx -y @e-rechnung-inbox/xrechnung-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"imysfylmz-xrechnung-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@e-rechnung-inbox/xrechnung-mcp"
],
"enabled": true
}
}
} openclaw mcp add imysfylmz-xrechnung-mcp --command npx --arg -y --arg @e-rechnung-inbox/xrechnung-mcp
mcp_servers:
imysfylmz-xrechnung-mcp:
command: "npx"
args: ["-y", "@e-rechnung-inbox/xrechnung-mcp"] {
"McpServers": {
"imysfylmz-xrechnung-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@e-rechnung-inbox/xrechnung-mcp"
]
}
}
} assistant mcp add imysfylmz-xrechnung-mcp -t stdio -c npx -a -y @e-rechnung-inbox/xrechnung-mcp
{
"mcpServers": {
"imysfylmz-xrechnung-mcp": {
"command": "npx",
"args": [
"-y",
"@e-rechnung-inbox/xrechnung-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 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 20 Sept 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 →
Dependencies 106 packages
| Packages resolved | 106 |
|---|---|
| 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 →
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.
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 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 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 20 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 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.