# Leborgneantoine Facturx MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.leborgneantoine%2Ffacturx
Registry id: `mcp-registry/io.github.leborgneantoine/facturx`
Status: live (checked 2026-10-26T22:36:45.923Z)

## Measurements (30 days)

- Uptime: 99.97%
- Checks: 4937
- Outages (90 days): 2

## Install

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

Claude Code:

```sh
claude mcp add --transport http leborgneantoine-facturx-mcp-server https://facturx.orvel.dev/mcp
```

## Tools (10)

- `check_invoice_parties`: Check a supplied seller AND buyer together, returning combined readiness and separate evidence. Use before generate_invoice; use check_party for one party and v
- `check_party`: Check exactly one seller or buyer's registry identifiers and readiness through EU Verify. Use to correct one party's identifiers; use check_invoice_parties to c
- `draft_credit_note`: Draft a type-381 credit note from an existing invoice, for all lines or selected quantities. Use to reverse an existing invoice's charges; use get_invoice_examp
- `embed_xml`: Combine a visual PDF you already have with CII XML into one Factur-X PDF/A-3. Use for an existing visual invoice; use generate_invoice to render invoice data or
- `explain_finding`: Turn a validation rule id into the invoice field to change and an example value. Use after validate_invoice or a generate_invoice rule error, not to validate an
- `extract_invoice`: Extract invoice parties, dates, lines, totals and VAT as JSON for bookkeeping or matching. Use validate_invoice for compliance; this performs no OCR or recalcul
- `generate_invoice`: Create an EN 16931 e-invoice from structured data: Factur-X PDF/A-3, CII XML, or UBL 2.1 XML. Use when you have the parties, lines and dates and need the docume
- `get_invoice_example`: Return a complete invoice or credit-note example to edit and pass to generate_invoice. Use this first, instead of inventing fields. No API key is required, and 
- `validate_invoice`: Check a Factur-X PDF, CII XML or UBL XML against EN 16931, and report the fields to fix. Use when the caller supplies a document, including after corrections; u
- `view_invoice_demo`: Demonstrate the engine on bundled synthetic samples only; never checks a user's invoice. Use for product evaluation without a key. To check a supplied document,

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.