# dev.invoicehub/invoicehub (remote · api.invoicehub.dev)

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

- Trust score: 71/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.invoicehub.dev`: 71/100 (this document), [markdown](https://verifymcp.io/servers/dev-invoicehub-invoicehub/api.md), [page](https://verifymcp.io/servers/dev-invoicehub-invoicehub/api)

## Channel facts

- Endpoint: `https://api.invoicehub.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 559 tokens (~139/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.dev-invoicehub-invoicehub]
url = "https://api.invoicehub.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-invoicehub-invoicehub": {
      "type": "remote",
      "url": "https://api.invoicehub.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-invoicehub-invoicehub --url https://api.invoicehub.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-invoicehub-invoicehub:
    url: "https://api.invoicehub.dev/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 70, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 63)

First indexed and scored.

## MCP tools (4)

### `validate_invoice` (~64 tokens)

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.

Input parameters:

- `xml` (string, required): Raw UBL 2.1 invoice XML.

### `generate_invoice` (~149 tokens)

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.

Input parameters:

- `buyer` (object, required)
- `currency` (string, required): ISO 4217, e.g. EUR.
- `dueDate` (string)
- `invoiceNumber` (string, required)
- `issueDate` (string, required): ISO date, e.g. 2026-06-19.
- `lines` (array, required)
- `payment` (object)
- `seller` (object, required)

### `convert_invoice` (~320 tokens)

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.

Input parameters:

- `document` (string, required): The source document: raw text for XML formats, base64 for binary formats (Factur-X).
- `from` (string, required): Source format id, e.g. "UBL_2.1".
- `to` (string, required): Target format id, e.g. "UN_CEFACT_CII", "XRechnung_UBL", "XRechnung_CII", or "Factur-X".

### `list_supported_formats` (~26 tokens)

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-invoicehub-invoicehub/api#diagnostics

## Score history

- 2026-08-03: 71
- 2026-08-02: 71
- 2026-08-01: 70
- 2026-07-31: 66
- 2026-07-30: 65
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 63

## Links

- Remote endpoint: https://api.invoicehub.dev/mcp
- Repository: https://github.com/einvoice-dev1/einvoice
- Website: https://invoicehub.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-invoicehub-invoicehub/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-invoicehub-invoicehub/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dev-invoicehub-invoicehub/api