Skip to content

InvoiceHub MCP server

Which MCP servers are InvoiceHub's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to InvoiceHub

Whose server it is
  • Registry namedev.invoicehub/invoicehubverified in the MCP registry

The registry name sits under invoicehub.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools4
  • Server calls itselfinvoicehub
  • Server version1.3.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 447 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Validate EU e-invoices against EN 16931 rules; Convert invoices between UBL, CII, XRechnung and Factur-X.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "Validate EU e-invoices against EN 16931 rules", the likely first call is validate_invoice.
  • For "Convert invoices between UBL, CII, XRechnung and Factur-X", the likely first call is convert_invoice.
  • Parameters are untyped or undescribed in 1 of 4 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer542 ms
  • Space in an agent's context≈ 715 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 96 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 4

What an agent can do with it

  • can do · Validate EU e-invoices against EN 16931 rules
  • can do · Convert invoices between UBL, CII, XRechnung and Factur-X
  • not sure · Generate compliant invoices from one JSON document

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-26
  • validate_invoice

    Validate an EU e-invoice XML string against the official EN 16931 Schematron. Accepts either syntax — UBL 2.1 (Invoice or CreditNote) or UN/CEFACT CII — and auto-detects which. A document declaring the XRechnung 3.0 CustomizationID is…

  • generate_invoice

    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…

  • convert_invoice

    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…

  • list_supported_formats

    List the e-invoice formats InvoiceHub validates today and what is on the roadmap.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "invoicehub": {
      "type": "http",
      "url": "https://api.invoicehub.dev/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http invoicehub https://api.invoicehub.dev/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.invoicehub.dev/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.