# Factur-X e-invoicing (remote · facturx.orvel.dev)

Generate, validate and read Factur-X / EN 16931 e-invoices (France, EU): PDF/A-3, CII, UBL 2.1.

- Trust score: 84/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `facturx.orvel.dev`: 84/100 (this document), [markdown](https://verifymcp.io/servers/leborgneantoine-facturx/facturx.md), [page](https://verifymcp.io/servers/leborgneantoine-facturx/facturx)

## Channel facts

- Endpoint: `https://facturx.orvel.dev/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.3`

## 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-09-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1406 tokens (~234/item across 6 items; 4 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (50% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Factur-X e-invoicing MCP server?

Factur-X e-invoicing is a hosted endpoint at https://facturx.orvel.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.

### Claude

```bash
claude mcp add --transport http leborgneantoine-facturx 'https://facturx.orvel.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "leborgneantoine-facturx": {
      "url": "https://facturx.orvel.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "leborgneantoine-facturx": {
      "type": "http",
      "url": "https://facturx.orvel.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.leborgneantoine-facturx]
url = "https://facturx.orvel.dev/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add leborgneantoine-facturx --url 'https://facturx.orvel.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  leborgneantoine-facturx:
    url: "https://facturx.orvel.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "leborgneantoine-facturx": {
      "Transport": "http",
      "Url": "https://facturx.orvel.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add leborgneantoine-facturx -t streamable-http -u 'https://facturx.orvel.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "leborgneantoine-facturx": {
      "type": "http",
      "url": "https://facturx.orvel.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-09-21 (score 84, +1)

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

### 2026-09-19 (score 83, +1)

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

### 2026-09-17 (score 82, +1)

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

### 2026-09-15 (score 81, +1)

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

### 2026-09-13 (score 80, +1)

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

### 2026-09-11 (score 79, +1)

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

### 2026-09-08 (score 78, +1)

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

### 2026-09-06 (score 77, +1)

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

## MCP tools (4)

### `generate_invoice` (~477 tokens)

Generate Factur-X invoice

Create a new, compliant e-invoice (Factur-X PDF/A-3, CII XML or UBL XML) from structured invoice data.

    Use when you have the invoice content (parties, lines, dates) and need the document. Do not use when you
    already have a visual PDF and a Factur-X XML to combine: call embed_xml. To check a document you did not
    create here, call validate_invoice; to read one, call extract_invoice.

    The result is validated (XSD + schematron for `check`) before it is returned; on failure the tool returns
    an error listing the failing rule ids (e.g. BR-CO-10, BR-FR-01) so you can fix the input and retry.
    Nothing is stored. Returns a text summary (number, totals, warnings) plus the document as an embedded
    resource: base64 PDF for facturx-pdf, XML text for cii-xml / ubl-xml.

Input parameters:

- `check` (string): Rule set the output must pass before it is returned: fr-ctc (default) = EN 16931 + French CTC rules (BR-FR-*), base = EN 16931 only (non-French sellers).
- `footer_text`: Optional footer text on the PDF
- `invoice` (required): Invoice data: seller, buyer, lines, dates, payment terms. Amounts are decimal strings ("1200.00"), dates ISO 8601. Totals and the VAT breakdown are computed. Full JSON Schema in the resource facturx:…
- `language`: Language of the visual PDF: fr or en
- `output`: facturx-pdf (default): PDF/A-3 with the visual invoice and the CII XML embedded, the format French platforms accept. cii-xml: the UN/CEFACT CII XML alone. ubl-xml: UBL 2.1 XML alone (Peppol-style).
- `profile`: Factur-X conformance level written in the XML: en16931 (default, full EN 16931 semantic model), extended (adds optional business terms), extended-ctc-fr (French B2B mandate profile), basicwl (no line…

### `embed_xml` (~228 tokens)

Embed Factur-X XML into a PDF

Combine a visual PDF you already have with a Factur-X (CII) XML into one PDF/A-3 Factur-X invoice.

    Use when the PDF is produced by your own system and you only need the compliant hybrid file. Do not use
    to create an invoice from data: call generate_invoice, which renders the PDF too. The XML is validated
    first and rejected with rule ids if it fails. Nothing is stored. Returns a text summary plus the PDF/A-3
    as a base64 embedded resource.

Input parameters:

- `check` (string): Rule set the XML must pass before embedding: fr-ctc (default, France) or base (EN 16931 only)
- `language`: Document language written in the PDF metadata: fr or en
- `pdf_base64` (string, required): Your existing visual invoice PDF (any PDF, will be converted to PDF/A-3), base64 encoded
- `xml` (string, required): Factur-X / CII XML text for the same invoice; must pass the `check` rules or the tool fails

### `validate_invoice` (~246 tokens)

Validate e-invoice

Check whether an existing e-invoice (Factur-X PDF, CII or UBL XML) is compliant, and report why not.

    Use on any document you did not produce with generate_invoice (supplier invoices, files from another
    system) or to re-check after a fix. Do not use to read the invoice content: call extract_invoice.
    Runs XSD then the EN 16931 schematron (plus French rules for fr-ctc). Read-only, nothing stored.
    Returns {valid, profile, findings[]} where each finding has the rule id (e.g. BR-CO-10), severity and
    message; a non-compliant document is a normal result, not an error.

Input parameters:

- `check` (string): fr-ctc (default): EN 16931 + French CTC rules (BR-FR-*). base: EN 16931 only.
- `document_base64`: Factur-X PDF (the embedded XML is read) or a CII/UBL XML file, base64 encoded
- `xml`: CII or UBL XML as plain text; alternative to document_base64, give exactly one

### `extract_invoice` (~183 tokens)

Extract e-invoice data

Read an e-invoice and return its business data as JSON: number, dates, seller, buyer, totals, VAT breakdown, lines.

    Use to get the content of a received invoice (Factur-X PDF, CII or UBL XML) for bookkeeping, matching
    or summaries. Does not judge compliance: call validate_invoice for that. Read-only, nothing stored.
    Returns {profile, fields{...}} and, with include_xml, the XML text.

Input parameters:

- `document_base64`: Factur-X PDF (the embedded XML is read) or a CII/UBL XML file, base64 encoded
- `include_xml` (boolean): Also return the raw XML text (large); default false returns only the parsed fields
- `xml`: CII or UBL XML as plain text; alternative to document_base64, give exactly one

## Diagnostics

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

## Score history

- 2026-09-21: 84
- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 78
- 2026-09-07: 77
- 2026-09-06: 77
- 2026-09-05: 76
- 2026-09-04: 76
- 2026-09-03: 75
- 2026-09-02: 33

## Common questions

### What is the Factur-X e-invoicing MCP server?

Factur-X e-invoicing is an MCP server listed in the public MCP registry as io.github.LeBorgneAntoine/facturx. Generate, validate and read Factur-X / EN 16931 e-invoices (France, EU): PDF/A-3, CII, UBL 2.1. This page covers its hosted endpoint (https://facturx.orvel.dev/mcp).

### Is the Factur-X e-invoicing MCP server safe to use?

Factur-X e-invoicing scores 84 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 Factur-X e-invoicing MCP server expose?

Factur-X e-invoicing exposes 4 tools: generate_invoice, embed_xml, validate_invoice, extract_invoice. Their descriptions and schemas cost roughly 1,134 tokens of context every time the server is loaded.

### Does the Factur-X e-invoicing MCP server require authentication?

Yes. Factur-X e-invoicing asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Factur-X e-invoicing MCP server still maintained?

Factur-X e-invoicing is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://facturx.orvel.dev/mcp
- Authorisation metadata: https://facturx.orvel.dev/.well-known/oauth-protected-resource/mcp
- Website: https://facturx.orvel.dev/docs/
- Changelog RSS feed: https://verifymcp.io/servers/leborgneantoine-facturx/facturx.xml
- Changelog JSON feed: https://verifymcp.io/servers/leborgneantoine-facturx/facturx.json
- HTML version of this page: https://verifymcp.io/servers/leborgneantoine-facturx/facturx