io.github.makririch/einvoice

NPM · EINVOICE-MCP · SCANNED AUG 3

XRechnung & ZUGFeRD: create, validate, and convert German e-invoices. EN 16931 compliant.

Available components

+21 this week 65 65 Trust /100

Trust breakdown (6 categories)

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 →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (103 of 107), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (103 of 107), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
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 111 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability56

AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 954 tokens (~159/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 Management23

Stability observed for 7 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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · einvoice-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add makririch-einvoice -- npx -y einvoice-mcp

# add to Codex CLI

codex mcp add makririch-einvoice -- npx -y einvoice-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "makririch-einvoice": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "einvoice-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add makririch-einvoice --command npx --arg -y --arg einvoice-mcp

# ~/.hermes/config.yaml

mcp_servers:
  makririch-einvoice:
    command: "npx"
    args: ["-y", "einvoice-mcp"]

// mcp.json

{
  "mcpServers": {
    "makririch-einvoice": {
      "command": "npx",
      "args": [
        "-y",
        "einvoice-mcp"
      ]
    }
  }
}

Changelog

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.

3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
2 Aug 26 +37
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Security disclosure: fail → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: unverified → good ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
1 Aug 26 +17
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Dependency health: partial → unverified ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
31 Jul 26 −37
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +20
- Tool coverage: unverified → 100 ▲ functional
28 Jul 26 −20
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
27 Jul 26 44

First indexed and scored.

Show 4 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 103 packages

103 packages in the resolved dependency tree · 103 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 6 exposed · ~954 tokens

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.

Tool Tokens

convert_format ~130

Konvertiert E-Rechnungen zwischen UBL (XRechnung), CII (ZUGFeRD) und JSON. Converts e-invoices between formats: ubl_to_cii, cii_to_ubl, ubl_to_json, cii_to_json, json_to_ubl, json_to_cii.

Input Output Examples

Name	Type	Req	Description
direction	string	yes	Konvertierungsrichtung
input	string	yes	Input-Daten: XML-String fuer ubl/cii, JSON-String fuer json
validate_output	boolean	—	Output nach Konvertierung validieren (nur fuer XML-Output)

No output schema declared.

No examples provided.

create_xrechnung ~307

Erstellt eine XRechnung (UBL 2.1 XML) aus strukturierten Daten. Konform zu EN 16931 + XRechnung 3.0.2. Creates a valid XRechnung XML from structured data.

Input Output Examples

Name	Type	Req	Description
bankName	string	—	Name der Bank
bic	string	—	BIC
buyer	object	yes	Rechnungsempfaenger
buyerReference	string	—	Leitweg-ID oder Kaeufer-Referenz (BT-10, Pflicht in XRechnung)
currency	string	—	Waehrung (ISO 4217)
dueDate	string	—	Faelligkeitsdatum (YYYY-MM-DD)
iban	string	—	IBAN fuer Zahlung
invoiceNumber	string	yes	Rechnungsnummer (eindeutig)
issueDate	string	yes	Rechnungsdatum (YYYY-MM-DD)
lineItems	array	yes	Rechnungspositionen
note	string	—	Freitext-Bemerkung
orderReference	string	—	Bestellnummer des Kaeufers (BT-13)
paymentMeansCode	string	—	Zahlungsart: 30=Ueberweisung, 58=SEPA-Ueberweisung, 59=SEPA-Lastschrift
paymentTerms	string	—	Zahlungsbedingungen (z.B. 'Zahlbar innerhalb von 30 Tagen')
seller	object	yes	Rechnungssteller

No output schema declared.

No examples provided.

create_zugferd ~237

Erstellt ZUGFeRD 2.3 CII XML (Factur-X). Returns CII XML for embedding into PDF/A-3. Creates ZUGFeRD-compatible e-invoice XML in CII format.

Input Output Examples

Name	Type	Req	Description
bic	string	—	BIC
buyer	object	yes	Rechnungsempfaenger
buyerReference	string	—	Leitweg-ID / Kaeufer-Referenz (BT-10)
currency	string	—	Waehrung (ISO 4217)
dueDate	string	—	Faelligkeitsdatum (YYYY-MM-DD)
iban	string	—	IBAN fuer Zahlung
invoiceNumber	string	yes	Rechnungsnummer (eindeutig)
issueDate	string	yes	Rechnungsdatum (YYYY-MM-DD)
lineItems	array	yes	Rechnungspositionen
note	string	—	Freitext-Bemerkung
orderReference	string	—	Bestellnummer des Kaeufers (BT-13)
paymentTerms	string	—	Zahlungsbedingungen
seller	object	yes	Rechnungssteller

No output schema declared.

No examples provided.

extract_data ~69

Extrahiert strukturierte Daten aus einer E-Rechnung (UBL-XML oder CII-XML). Extracts structured data from an e-invoice XML.

Input Output Examples

Name	Type	Req	Description
base64	string	—	Base64-kodierte XML-Datei
xml	string	—	E-Rechnung XML als String

No output schema declared.

No examples provided.

get_format_info ~97

Gibt Informationen ueber E-Rechnungs-Formate, Pflichtfelder, Steuer-Kategorien, Einheiten-Codes und gesetzliche Fristen zurueck. Useful reference for creating valid invoices.

Input Output Examples

Name	Type	Req	Description
format	string	—	Welches Format abfragen
topic	string	—	overview=Formatbeschreibung, required_fields=Pflichtfelder, tax_categories=USt-Kategorien, unit_codes=Einheiten, deadlines=Fristen

No output schema declared.

No examples provided.

validate_invoice ~114

Prueft ob XML eine gueltige E-Rechnung (XRechnung/ZUGFeRD) ist. Validiert Syntax, Pflichtfelder und deutsche Business-Regeln (BR-DE). Validates e-invoice XML.

Input Output Examples

Name	Type	Req	Description
base64	string	—	Base64-kodierte XML-Datei
level	string	—	Validierungstiefe: syntax=well-formed, schema=Struktur, full=inkl. BR-DE-Regeln
xml	string	—	E-Rechnung XML als String

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug