mcp-server-erechnung
Related Servers
Alternatives to mcp-server-erechnung
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables AI assistants and agents to create, validate, read and convert German and EU e-invoices in ZUGFeRD, XRechnung and Factur-X formats, including extracting structured data from scanned or PDF invoices and embedding XML into PDF/A-3 files. It can run as a hosted remote server or locally, with each request authenticated by the caller's own API token.1024 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables users to detect, parse, validate, and render European e-invoices such as XRechnung, ZUGFeRD, Factur-X, Peppol BIS Billing 3.0, EN 16931 UBL/CII, and Polish KSeF FA(3) using official rule sets. It is a remote, stateless Streamable HTTP server with tools for invoice inspection, compliance validation, and HTML/PDF rendering.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to locally parse, validate, audit, explain, generate, and convert XRechnung and ZUGFeRD/Factur-X e-invoices using official rule sets, fully offline with no API keys required.Apache 2.0
- AlicenseAqualityDmaintenanceMCP server for German e-invoice compliance (XRechnung 3.0 & ZUGFeRD 2.x) enabling AI agents to validate, generate, parse, and check compliance of electronic invoices per EN 16931.61MIT
- AlicenseAqualityAmaintenanceCreate and check EU e-invoices (XRechnung, ZUGFeRD / Factur-X PDF, Peppol BIS, UBL, CII) on your own machine. Validation runs the official KoSIT, CEN and Peppol rules, and its verdicts match the official KoSIT validator 100% on the official test invoices. Free, open source, no API key.67587 npm4Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to extract invoice data from existing PDFs and create EN 16931-compliant ZUGFeRD/Factur-X e-invoices or XRechnung XML locally, without uploading documents.497 npm3MIT
TDQS
Scored across 5 tools
generate_erechnung, embed_zugferd_pdf, and magic_convert_pdf all ultimately produce a ZUGFeRD PDF/A-3b hybrid invoice, and the boundaries between 'generate from JSON', 'upgrade PDF+JSON', and 'convert flat PDF' are not fully crisp—magic_convert appears to combine parse+embed. validate_erechnung and parse_erechnung are clearly distinct, and the descriptions do help an agent pick the right entry point, but there is real overlap in the generation/conversion cluster.
generate_/validate_/parse_erechnung follow a clean verb+domain pattern, but the set drifts to a different object name in embed_zugferd_pdf and a non-standard quirky verb in magic_convert_pdf. Readable but not one predictable convention across all five tools.
Five tools is well within a healthy scope and each maps to a recognizable invoice operation (generate, validate, parse, embed, convert). Slight over-partitioning in the generation/embedding area keeps it from being a perfect fit, but nothing feels padded or missing count-wise.
The core lifecycle is covered: create both ZUGFeRD and XRechnung from JSON, validate against EN 16931/KoSIT/veraPDF, parse inbound invoices, embed and convert legacy PDFs. Minor gaps remain—no direct ZUGFeRD↔XRechnung format conversion and no preview/readable rendering—but agents can work around these via generate with the appropriate format flag.