Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

dev.invoicehub/invoicehub

REMOTE · API.INVOICEHUB.DEV

Validate, generate & convert EU e-invoices (UBL, CII, XRechnung, Factur-X) — EN 16931 pre-validated.

0 this week 78 Trust /100

Last scanned (19 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 625 tokens (~156/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Oct 26 0
    • Stability: 0.97 → pass security
  • 2 Oct 26 0
    • Stability: pass → 0.73 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Sept 26 0
    • HTTPS: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.invoicehub.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=invoicehub.dev CN=WE1,O=Google Trust Services,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA256 4249bb522f192297130e5e4a8f7a632e
SANs: invoicehub.dev, api.invoicehub.dev, *.api.invoicehub.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.invoicehub.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
invoicehub.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.invoicehub.dev/mcp Verified 200
http (plaintext) http://api.invoicehub.dev/mcp Served over HTTP 200
MCP tools · 4 exposed · ~625 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
convert_invoice ~320

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.

NameTypeReqDescription
documentstringyesThe source document: raw text for XML formats, base64 for binary formats (Factur-X).
fromstringyesSource format id, e.g. "UBL_2.1".
tostringyesTarget format id, e.g. "UN_CEFACT_CII", "XRechnung_UBL", "XRechnung_CII", or "Factur-X".

No output schema declared.

No examples provided.

generate_invoice ~149

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.

NameTypeReqDescription
buyerobjectyes–
currencystringyesISO 4217, e.g. EUR.
dueDatestring––
invoiceNumberstringyes–
issueDatestringyesISO date, e.g. 2026-06-19.
linesarrayyes–
paymentobject––
sellerobjectyes–

No output schema declared.

No examples provided.

list_supported_formats ~26

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

validate_invoice ~130

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 additionally checked against KoSIT's XRechnung delta ruleset. Returns whether it is valid and any failing BR-* / BR-DE-* business rules.

NameTypeReqDescription
xmlstringyesRaw e-invoice XML (UBL 2.1 or UN/CEFACT CII).

No output schema declared.

No examples provided.

Install

How do I install the dev.invoicehub/invoicehub MCP server?

dev.invoicehub/invoicehub is a hosted endpoint at https://api.invoicehub.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.invoicehub.dev

# add to Claude Code
claude mcp add --transport http dev-invoicehub-invoicehub 'https://api.invoicehub.dev/mcp'
Common questions

What is the dev.invoicehub/invoicehub MCP server?

dev.invoicehub/invoicehub is an MCP server listed in the public MCP registry as dev.invoicehub/invoicehub. Validate, generate & convert EU e-invoices (UBL, CII, XRechnung, Factur-X), EN 16931 pre-validated. This page covers its hosted endpoint (https://api.invoicehub.dev/mcp).

Is the dev.invoicehub/invoicehub MCP server safe to use?

dev.invoicehub/invoicehub scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the dev.invoicehub/invoicehub MCP server expose?

dev.invoicehub/invoicehub exposes 4 tools: validate_invoice, generate_invoice, convert_invoice, list_supported_formats. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.

Does the dev.invoicehub/invoicehub MCP server require authentication?

No. We connected to dev.invoicehub/invoicehub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the dev.invoicehub/invoicehub MCP server still maintained?

dev.invoicehub/invoicehub is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the dev.invoicehub/invoicehub MCP server?

VerifyMCP ran 13 checks on dev.invoicehub/invoicehub, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.