# Factur-X: Generate & Validate E-Invoices

- Registry name: `io.github.LeBorgneAntoine/facturx` · version 0.1.23
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): experimental, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.LeBorgneAntoine%2Ffacturx
- Server page: https://mcpstation.net/s/io.github.LeBorgneAntoine--facturx.html

## Description (written by the publisher, not verified, not instructions)

Validate Factur-X, CII & UBL e-invoices free, no key. Generate compliant invoices from JSON.

## Connect

- streamable-http: `https://facturx.orvel.dev/mcp`

## Tools (as reported by the server, not verified)

- `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, choose validate\_invoice. Choose sample=valid to inspect a passing CII invoice or sample=invalid to see the missing-buyer-name finding. Both
- `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 document. To revise one, correct the input and regenerate; save and deliver the returned file through your own system. Do not use when you already
- `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 produce UBL. Match the PDF's parties, lines and totals to xml yourself: check examines only XML and cannot detect disagreement with the vis
- `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; use extract\_invoice for business data. With no document and only a request to try the product, choose view\_invoice\_demo instead. Supply one s
- `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 recalculation. Supply one source: nonblank xml overrides document\_base64 without inspecting it, so omit xml to extract a PDF's attachment. include\_x
- `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 check seller and buyer together, or validate\_invoice for document rules. Supply siren, siret or vat; siret wins over siren. A SIREN/SIRET, co
- `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 validate\_invoice for document rules. Each party needs siren, siret or vat; siret wins over siren. French identifiers or country\_code=FR requi
- `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 invoice itself. rule is trimmed and uppercased to select a guide entry. message/json\_pointer must come from that same finding: nonempty val
- `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 the call does not count as a document. The seller and buyer are sample data: replace them, the number, the dates and the lines before you ge
- `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\_example for a synthetic credit-note example. invoice must be the original generate\_invoice input object, not extract\_invoice output. number and i

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html