FacturX (Factur-X / ZUGFeRD e-invoicing)
Related Servers
Alternatives to FacturX (Factur-X / ZUGFeRD e-invoicing)
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceRead and check European e-invoices (Factur-X, ZUGFeRD, XRechnung, UBL, CII) from an AI assistant: contents in plain text plus an EN 16931 consistency check.2MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to locate invoice files, extract embedded ZUGFeRD/Factur-X XML from PDF/A-3 documents, and validate compliance with § 14 UStG and EN 16931, including direct PDF invoice checks.31MIT

InvoiceXMLofficial
AlicenseNot gradedqualityBmaintenanceInvoiceXML brings e-invoice compliance to your AI agent. Create, validate, convert, render, and extract structured invoices across UBL (Peppol BIS Billing 3.0, used worldwide), CII, Factur-X, ZUGFeRD, and XRechnung, all checked against the EN 16931 standard and official Schematron rules. Ask your assistant to generate a compliant invoice, validate one for errors, or convert between formats, with n5MIT- 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
- AlicenseAqualityDmaintenanceValidates EU electronic invoices (Peppol, XRechnung, FatturaPA, etc.) and explains validation error codes, enabling AI coding agents to check invoice validity and get fixes before rejection.346 npmMIT

rechnungsapi-mcpofficial
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.1020 npmMIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: dry-run readiness check on ERP JSON, final file generation, validation of existing PDF/XML files, and error/rule explanation. The descriptions explicitly enforce sequencing (dry_run before convert) and distinguish input types, leaving little room for misselection.
All tools consistently use the facturx_ prefix followed by snake_case verb or verb_noun names: dry_run, convert, validate, explain_error. The pattern is predictable throughout the small set.
Four tools are well scoped for a focused e-invoicing conversion server: preflight, generate, validate, and explain. Each tool earns its place, and there is no redundant or trivial surface.
The core lifecycle is covered: readiness check, conversion, validation, and error explanation. Minor gaps exist, such as no tool for account/quota status, listing supported validation targets, or extracting invoice fields from an existing file, but these are workaroundable.