mcp server
invoicehub
Validate, generate & convert EU e-invoices (UBL, CII, XRechnung, Factur-X) — EN 16931 pre-validated.
Description as published by the maintainer. Source
- version 1.3.0
- archived
- document understanding
- voice
archived — The linked repository returns 404. It was deleted, renamed or made private. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
convert_invoice(to, from, document)- Convert an e-invoice between formats via the shared EN 16931 canonical model: parse the source document, re-serialize as the target, and validate the result before returning it — never a document that has not been checked. Format ids: "UBL_2.1" (OASIS UBL, the universal Peppol/EN16931 baseline), "UN_CEFACT_CII" (UN/CEFACT Cross Industry Invoice, required syntax for Chorus Pro/France and many ERP back-ends), "XRechnung_UBL" / "XRechnung_CII" (Germany's mandatory B2G format, XRechnung 3.0 — required for invoicing German public-sector buyers), "Factur-X" (France/Germany hybrid PDF+XML — a human-readable PDF/A-3 with the structured invoice embedded, common for French B2B). Binary formats (Factur-X) are base64 in both directions. Requires an API key on the Pro plan or above for any target beyond plain UBL_2.1 — call list_supported_formats to see current availability. Required: from, to, document.
generate_invoice(buyer, lines, seller, dueDate, payment, currency, issueDate, invoiceNumber)- Generate an EN 16931-conformant UBL 2.1 invoice from structured fields. The result is self-validated before being returned. Provide seller, buyer, and at least one line; for standard-rated (category "S") lines include a vatRate and the seller vatId. Required: invoiceNumber, issueDate, currency, seller, buyer, lines.
list_supported_formats- List the e-invoice formats InvoiceHub validates today and what is on the roadmap.
validate_invoice(xml)- Validate a UBL 2.1 invoice (or credit note) XML string against the official EN 16931 Schematron. Returns whether it is valid and any failing BR-* business rules. Required: xml.
Last successful function declaration observed on . Source: https://api.invoicehub.dev/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.invoicehub.dev/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.3.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-27 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-27 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | not_found | GitHub returned 404 for the repository the maintainer listed. The project was deleted, renamed or made private, so the listing points at nothing. | as of fetch | GitHub | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.invoicehub.dev | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | api.invoicehub.dev |
Where to get it
Also from einvoice-dev1
-
io.github.einvoice-dev1/archsteer
— last commit 2026-07-30
Architecture governance for AI agents: query the live model, get target patterns, check files.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json