beliq-mcp
OfficialRelated Servers
Alternatives to beliq-mcp
No user-submitted related servers found.
Related Servers
- 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 gradedqualityDmaintenanceEU e-invoice validation, as a developer API. Check whether an electronic invoice conforms to EN 16931 — the European standard behind France, Germany, Belgium, Poland and the 2030 ViDA mandate — with a single REST call. Structured JSON errors mapped to the official BR-* business rules. No enterprise sales call required.MIT
- 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

InvoiceInofficial
AlicenseAqualityBmaintenanceReads and validates any European e-invoice a business receives — XRechnung, UBL, CII, ZUGFeRD/Factur-X PDF, Peppol BIS 3, FatturaPA, KSeF FA(3) — into canonical EN 16931 JSON with plain-language fix hints in EN/DE/PL/IT/FR, plus PDF, CSV and DATEV export. Nothing is stored; works without a key on a small daily quota.5MIT
invowerkofficial
AlicenseNot gradedqualityBmaintenanceEnables creating ZUGFeRD PDFs and XRechnung invoices and validating ZUGFeRD/Factur-X, XRechnung (KoSIT), and Peppol BIS e-invoices through an MCP endpoint, returning validation reports.MIT- AlicenseAqualityBmaintenanceCheck, convert and explain Factur-X / ZUGFeRD e-invoices from your AI assistant: validate a PDF against EN 16931 or the French 2026 rules, dry-run or convert an invoice to Factur-X, and get a plain explanation of any validation error.24MIT
TDQS
Scored across 2 tools
The two tools have completely different purposes: one is a simple credential and quota check, the other validates e-invoices. There is no overlap or ambiguity between them.
Both tools follow a consistent 'beliq_verb_noun' pattern (check_account, validate_einvoice), which is clear and predictable.
With only two tools, the server feels very minimal. While the scope is limited to validation and account status, one might expect additional supporting tools (e.g., listing supported formats or checking ruleset versions). However, the count is not extreme.
For the stated goal of validating EU e-invoices, the two tools cover the essential workflow: credential check and document validation. Minor gaps exist, such as no tool to retrieve ruleset metadata or list supported profiles, but the core functionality is present.