Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.cmendezs/mcp-einvoicing-de

PYPI · MCP-EINVOICING-DE

German e-invoicing MCP server: ZUGFeRD 2.x, XRechnung 3.x, EN 16931, KoSIT validation, Peppol.

Available components

−15 this week 79 Trust /100

Last scanned (19 hours ago)

Scores higher than 78% of PyPI servers

Category Finance and Payments

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 2 of 35 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to cmendezs/mcp-einvoicing-de). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 52 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 4372 tokens (~87/item across 50 items; 50 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "peppol_send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 51 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 2 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 22 Oct 26 +1

    No change was recorded against any check on this day. Supply Chain Security went from 99 to 100.

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 4 Nov 2026 · Analysed pypi/mcp-einvoicing-de@0.11.4

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo cmendezs/mcp-einvoicing-de
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/cmendezs/mcp-einvoicing-de/.github/workflows/publish.yml@refs/tags/v0.11.4
Rekor log index 2805185564
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:fdce7cb3946a3242751eb05225f3eb46df20ced7a35ea0893ed8e57a155fc9fb

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 35 packages
Packages resolved 35
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 50 exposed · ~4,293 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. 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 →

Tool Tokens
build_mls_message ~291

Build a document-level MLS response and return it base64-encoded. For per-line responses, build the document directly with `mcp_einvoicing_core.peppol.mls.build_mls`.

NameTypeReqDescription
descriptionstring–Optional human-readable response text.
document_reference_idstringyesThe SBDH ``InstanceIdentifier`` of the source message this MLS reports on.
issue_datestringyesISO date string, e.g. "2026-08-23".
issue_timestring–Optional ISO time string, e.g. "12:00:00Z".
mls_idstringyesThe ``cbc:ID`` of this MLS document.
receiver_scheme_idstringyesICD scheme of the receiving endpoint (normally the original message's SBDH ``MLS_TO`` scheme).
receiver_valuestringyesReceiving endpoint value.
response_codestringyes"AB" (Acknowledged), "AP" (Accepted), or "RE" (Rejected).
sender_scheme_idstringyesICD scheme of the sending Access Point's endpoint.
sender_valuestringyesSending Access Point's endpoint value.
status_reason_codestring–Optional: "SV", "BV", "BW", or "FD" (required by the Schematron when response_code is "RE").

Structured output declared, but exposes no named fields.

No examples provided.

check_allowance_reason_code ~30

Check whether *code* is a recognized allowance reason code.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_charge_reason_code ~29

Check whether *code* is a recognized charge reason code.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_country_code ~36

Check whether *code* is a recognized ISO 3166-1 alpha-2 country code.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_currency_code ~31

Check whether *code* is a recognized ISO 4217 currency code.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_document_name_code ~33

Check whether *code* is a recognized UNCL1001 document name code.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_document_type_id_in_codelist ~95

Check whether a (scheme, value) pair is a recognized Peppol document type identifier. Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`). Searches all entries regardless of state, so a historical (deprecated or removed) document type is still reported as found.

NameTypeReqDescription
schemestringyes–
valuestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_eas_code ~30

Check whether *code* is a recognized Electronic Address Scheme code.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_icd_code ~32

Check whether *code* is a recognized ISO 6523 ICD code.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_item_type_code ~30

Check whether *code* is a recognized item type identification code.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_mime_code ~31

Check whether *code* is a recognized MIME type for embedded attachments.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_participant_id_scheme_in_codelist ~74

Check whether a 4-digit ISO 6523 ICD code (e.g. "0208") is a recognized Peppol scheme. Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

NameTypeReqDescription
icdstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_payment_means_code ~34

Check whether *code* is a recognized UNCL4461 payment means code.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_process_id_in_codelist ~68

Check whether a (scheme, value) pair is a recognized Peppol process identifier. Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

NameTypeReqDescription
schemestringyes–
valuestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_reference_qualifier_code ~35

Check whether *code* is a recognized UNCL1153 reference qualifier code.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_vat_category_code ~34

Check whether *code* is a recognized UNCL5305 VAT category code.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_vatex_code ~32

Check whether *code* is a recognized VATEX VAT exemption reason code.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

datev_export ~206

Export a ZUGFeRD invoice to DATEV CSV format (EXTF 700, Buchungsstapel). Produces a CSV file importable by DATEV Belegtransfer or DATEV Rechnungswesen. Maps invoice line items to DATEV booking records with configurable accounts.

NameTypeReqDescription
client_numberstring–DATEV Mandantennummer (client number).
consultant_numberstring–DATEV Beraternummer (consultant number).
fiscal_year_startstring–Fiscal year start date (YYYYMMDD). Defaults to Jan 1 of invoice year.
invoiceobjectyesZUGFeRDInvoice data to export.
receivable_accountstring–DATEV receivable account number (Debitorenkonto). Default: 10000.
revenue_accountstring–DATEV revenue account number (Erloskonto). Default: 8400 (SKR 03, 19% USt).

Structured output declared, but exposes no named fields.

No examples provided.

get_en16931_codelist_version ~32

Report the CEF EN 16931 code-list release version(s) currently configured locally.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_peppol_codelist_version ~32

Report the OpenPeppol eDEC code list release version(s) currently configured locally.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

invoice_convert ~219

Convert a ZUGFeRD or XRechnung invoice to a different profile or syntax. Supports ZUGFeRD profile upgrades and downgrades, ZUGFeRD <-> XRechnung conversion, and cross-syntax CII <-> UBL transformation. Profile downgrades may result in data loss; set allow_data_loss=True to permit this.

NameTypeReqDescription
allow_data_lossboolean–If True, allow profile downgrades that discard data. Discarded fields are listed in the output. If False and data loss would occur, the conversion is rejected.
target_profilestringyesOne of: MINIMUM, BASIC_WL, BASIC, EN_16931, EXTENDED, XRECHNUNG.
target_syntaxstring–Target syntax: 'CII' or 'UBL'. UBL is only valid for XRECHNUNG.
xml_base64––Base64-encoded XML bytes.
xml_content––Raw XML string of the source invoice.

Structured output declared, but exposes no named fields.

No examples provided.

invoice_create ~426

Generate a ZUGFeRD 2.x or XRechnung 3.x invoice in XML (CII or UBL) format. Supports all ZUGFeRD profiles: MINIMUM, BASIC_WL, BASIC, EN_16931, EXTENDED. For XRechnung, set profile to XRECHNUNG and choose CII or UBL syntax. When the buyer is a German VAT-registered business (DE-prefixed VAT id), the Wachstumschancengesetz B2B mandate (effective 2025-01-01, §14 Abs. 2 UStG) requires a structured EN 16931 invoice. Non-XML output is rejected unless transitional_period_opt_in is set to True (allowed only 2025-2026 with the buyer's written consent).

NameTypeReqDescription
invoiceobjectyesInvoice data matching the ZUGFeRDInvoice schema. Set invoice.profile to XRECHNUNG to produce an XRechnung invoice.
output_formatstring–'xml' (default) or 'pdf' (ZUGFeRD hybrid PDF/A-3).
pretty_printboolean–Pretty-print the XML output.
syntaxstring–XML syntax: 'CII' (default) or 'UBL' (XRechnung only).
transitional_period_opt_inboolean–Acknowledge the Wachstumschancengesetz transitional period (2025-2026) and explicitly permit non-XML output for a German VAT-registered buyer. Set to True only when the buyer has agreed in writing to…

Structured output declared, but exposes no named fields.

No examples provided.

invoice_parse ~154

Extract structured data from a ZUGFeRD 2.x or XRechnung 3.x invoice. Accepts raw XML (CII or UBL), base64-encoded XML, or base64-encoded PDF (ZUGFeRD hybrid — the XML is extracted from the PDF/A-3 attachment). Returns a structured JSON object matching the invoice data model.

NameTypeReqDescription
include_raw_xmlboolean–Include the raw XML string in the response.
pdf_base64––Base64-encoded PDF bytes. The tool will extract the embedded XML attachment (ZUGFeRD hybrid PDF/A-3).
xml_base64––Base64-encoded XML bytes.
xml_content––Raw XML string.

Structured output declared, but exposes no named fields.

No examples provided.

invoice_validate ~427

Validate a ZUGFeRD 2.x or XRechnung 3.x invoice XML. Checks against EN 16931 rules and German KoSIT Schematron rules (BR-DE-* business rules). Returns a structured validation report with errors and warnings. Supports all ZUGFeRD profiles (MINIMUM through EXTENDED) and XRechnung (CII and UBL syntax). Profile and syntax are auto-detected if not specified. By default this validator runs entirely locally (Schematron only). Set cloud_validate=True (or EINVOICING_DE_KOSIT_ENABLE=1) to opt in to sending the invoice XML to a remote KoSIT endpoint. Doing so egresses the full invoice payload.

NameTypeReqDescription
cloud_validateboolean–Opt in to sending the invoice XML to a remote KoSIT endpoint (egresses the full invoice payload). Local Schematron only by default.
kosit_strictboolean–If True, fail hard when the KoSIT cloud validator is unreachable instead of falling back to local Schematron.
profile––Override profile detection. One of: MINIMUM, BASIC_WL, BASIC, EN_16931, EXTENDED, XRECHNUNG. If omitted, auto-detected from the XML GuidelineID.
strictboolean–If True, warnings are also reported. If False, only errors are returned.
syntax––Override syntax detection. One of: CII, UBL. If omitted, auto-detected from the XML root element namespace.
use_local_only––[Deprecated] Use cloud_validate instead. use_local_only=True is equivalent to cloud_validate=False, which is now the default; this alias is retained for one release and will be removed.
xml_base64––Base64-encoded XML bytes of the invoice.
xml_content––Raw XML string of the invoice to validate. Provide either xml_content or xml_base64, not both.

Structured output declared, but exposes no named fields.

No examples provided.

list_allowance_reason_codes ~26

List allowance reason codes from the CEF EN 16931 code list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_charge_reason_codes ~25

List charge reason codes from the CEF EN 16931 code list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_country_codes ~32

List ISO 3166-1 alpha-2 country codes from the CEF EN 16931 code list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_currency_codes ~27

List ISO 4217 currency codes from the CEF EN 16931 code list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_document_name_codes ~29

List UNCL1001 document name codes from the CEF EN 16931 code list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_document_type_ids ~69

List Peppol document type identifiers from the OpenPeppol eDEC code list. Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

NameTypeReqDescription
active_onlyboolean–When True (default), omit deprecated/removed entries.

Structured output declared, but exposes no named fields.

No examples provided.

list_eas_codes ~30

List Electronic Address Scheme (EAS) codes from the CEF EN 16931 code list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_icd_codes ~28

List ISO 6523 ICD codes from the CEF EN 16931 code list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_item_type_codes ~26

List item type identification codes from the CEF EN 16931 code list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_mime_codes ~18

List recognized MIME types for embedded attachments.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_participant_id_schemes ~120

List Peppol participant identifier (ICD) schemes from the OpenPeppol eDEC code list. Requires EINVOICING_PEPPOL_CODELIST_DIR to point at a local copy of the eDEC "Participant Identifier Schemes" GeneriCode export (not bundled with this package, no confirmed redistribution rights, see `mcp_einvoicing_core.peppol.codelists` module docstring).

NameTypeReqDescription
active_onlyboolean–When True (default), omit deprecated/removed entries.

Structured output declared, but exposes no named fields.

No examples provided.

list_payment_means_codes ~30

List UNCL4461 payment means codes from the CEF EN 16931 code list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_process_ids ~67

List Peppol process identifiers from the OpenPeppol eDEC code list. Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

NameTypeReqDescription
active_onlyboolean–When True (default), omit deprecated/removed entries.

Structured output declared, but exposes no named fields.

No examples provided.

list_reference_qualifier_codes ~31

List UNCL1153 reference qualifier codes from the CEF EN 16931 code list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_spis_use_case_ids ~73

List Peppol SPIS use case identifiers from the OpenPeppol eDEC code list. Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

NameTypeReqDescription
active_onlyboolean–When True (default), omit deprecated/removed entries.

Structured output declared, but exposes no named fields.

No examples provided.

list_vat_category_codes ~30

List UNCL5305 VAT category codes from the CEF EN 16931 code list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_vatex_codes ~30

List VATEX (VAT exemption reason) codes from the CEF EN 16931 code list.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

peppol_directory_search ~188

Search the Peppol Directory for registered participants. Public, unauthenticated search (no relation to SMP lookup). At least one of q/participant/name/country/doctype must be supplied.

NameTypeReqDescription
country––Exact match on ISO 3166-2 country code.
doctype––Exact match on a full document type identifier URN.
environmentstring–"production" or "test".
name––Partial match on business entity name (min. 3 characters).
participant––Exact match on a scheme-qualified participant ID (e.g. "iso6523-actorid-upis::0208:0123456789").
q––General purpose query term, matched across all fields.
result_page_countinteger–Results per page.
result_page_indexinteger–0-based result page index.

Structured output declared, but exposes no named fields.

No examples provided.

peppol_get_service_endpoint ~153

Fetch the AS4 endpoint for a Peppol participant's document type. Resolves the SMP hostname via DNS, then fetches service metadata for *document_type_id*. If the SMP returns a redirect, the result's `redirect_url` is set and `endpoint_url` is None; callers must not follow more than one redirect hop (SMP 1.4.0 §3.2).

NameTypeReqDescription
document_type_idstring–Peppol document type identifier URN (default: BIS Billing 3.0 invoice).
environmentstring–"production" or "test".
identifierstringyesPeppol participant ID or adaptable national identifier.

Structured output declared, but exposes no named fields.

No examples provided.

peppol_lookup_participant ~120

Check whether a business is registered on the Peppol network. Performs a DNS-over-HTTPS U-NAPTR lookup followed by an SMP service-group request to determine registration status and the list of supported document type identifiers.

NameTypeReqDescription
environmentstring–"production" or "test".
identifierstringyesPeppol participant ID ("<scheme>:<value>") or a bare national identifier this server knows how to adapt (e.g. a VAT number, if a national identifier adapter is configured).

Structured output declared, but exposes no named fields.

No examples provided.

peppol_send ~208

Send a UBL/CII invoice to a Peppol participant via AS4. Looks up the recipient's AS4 endpoint (SMP), builds the ebMS3/AS4 envelope, and transmits it using the supplied signing credentials.

NameTypeReqDescription
certificate_pathstringyesPath to the PEM-encoded signing certificate.
document_type_idstring–Peppol document type identifier URN (default: BIS Billing 3.0 invoice).
environmentstring–"production" or "test".
invoice_xml_base64stringyesBase64-encoded UBL or CII invoice XML.
private_key_passwordstring–Optional password for the private key.
private_key_pathstringyesPath to the PEM-encoded private key.
recipient_identifierstringyesPeppol participant ID or adaptable national identifier of the receiver.
sender_idstringyesPeppol AP identifier of the sender.

Structured output declared, but exposes no named fields.

No examples provided.

resolve_peppol_dns ~94

Resolve the SMP hostname for a Peppol participant via DNS only. Performs the raw U-NAPTR (SML) lookup without fetching the SMP service group, useful for diagnosing whether a participant is registered in the SML independently of SMP reachability.

NameTypeReqDescription
environmentstring–"production" or "test".
identifierstringyesPeppol participant ID or adaptable national identifier.

Structured output declared, but exposes no named fields.

No examples provided.

tax_rules ~170

Query German VAT rules for e-invoicing. Returns structured information about VAT rates (19%, 7%), VAT category codes, reverse charge rules under §13b UStG, zero-rate and exemption provisions (§4 UStG), intra-community supply rules, and VATEX exemption reason codes. For use when building invoice creation logic or validating VAT treatment.

NameTypeReqDescription
context––Optional context about the transaction, e.g. 'construction services' or 'intra-community supply'. Used to filter relevant rules.
querystringyesWhat to look up. Examples: 'reverse_charge', 'rates', 'exemptions', 'kleinunternehmer', '13b', 'zero_rate', 'vatex_codes', or a free-text question about German VAT.

Structured output declared, but exposes no named fields.

No examples provided.

validate_eusr_report ~69

Validate a Peppol End User Statistics Report (EUSR) document. Runs XSD structural validation, then Schematron business rules (requires the ``[xslt2]`` optional extra).

NameTypeReqDescription
report_xml_base64stringyesBase64-encoded EUSR XML document.

Structured output declared, but exposes no named fields.

No examples provided.

validate_mls_message ~92

Validate a Peppol Message Level Status (MLS) document. Runs the bundled MLS Schematron rules (requires the ``[xslt2]`` optional extra). No bespoke MLS XSD exists — full UBL 2.1 XSD validation is out of scope.

NameTypeReqDescription
mls_xml_base64stringyesBase64-encoded MLS (UBL ApplicationResponse-2) XML.

Structured output declared, but exposes no named fields.

No examples provided.

validate_tsr_report ~67

Validate a Peppol Transaction Statistics Report (TSR) document. Runs XSD structural validation, then Schematron business rules (requires the ``[xslt2]`` optional extra).

NameTypeReqDescription
report_xml_base64stringyesBase64-encoded TSR XML document.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.cmendezs/mcp-einvoicing-de server?

io.github.cmendezs/mcp-einvoicing-de runs locally as a PyPI package, launched with uvx mcp-einvoicing-de. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-einvoicing-de

# add to Claude Code
claude mcp add cmendezs-mcp-einvoicing-de -- uvx mcp-einvoicing-de
Common questions

What is the io.github.cmendezs/mcp-einvoicing-de server?

io.github.cmendezs/mcp-einvoicing-de is listed in the public MCP registry as io.github.cmendezs/mcp-einvoicing-de. German e-invoicing MCP server: ZUGFeRD 2.x, XRechnung 3.x, EN 16931, KoSIT validation, Peppol. This page covers its PyPI package (mcp-einvoicing-de).

Is the io.github.cmendezs/mcp-einvoicing-de server safe to use?

io.github.cmendezs/mcp-einvoicing-de scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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.cmendezs/mcp-einvoicing-de server expose?

io.github.cmendezs/mcp-einvoicing-de exposes 50 tools: invoice_create, invoice_validate, invoice_parse, invoice_convert, datev_export, and 45 more. Their descriptions and schemas cost roughly 4,293 tokens of context every time the server is loaded.

Is the io.github.cmendezs/mcp-einvoicing-de server still maintained?

io.github.cmendezs/mcp-einvoicing-de is still listed as active in the MCP registry. We last reached this channel on 4 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.cmendezs/mcp-einvoicing-de server under?

io.github.cmendezs/mcp-einvoicing-de declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.