Factur-X e-invoicing
REMOTE · FACTURX.ORVEL.DEV · SCANNED SEP 20
Generate, validate and read Factur-X / EN 16931 e-invoices (France, EU): PDF/A-3, CII, UBL 2.1.
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
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 6 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
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.
remote · facturx.orvel.dev
claude mcp add --transport http leborgneantoine-facturx 'https://facturx.orvel.dev/mcp'
{
"mcpServers": {
"leborgneantoine-facturx": {
"url": "https://facturx.orvel.dev/mcp"
}
}
} {
"servers": {
"leborgneantoine-facturx": {
"type": "http",
"url": "https://facturx.orvel.dev/mcp"
}
}
} [mcp_servers.leborgneantoine-facturx] url = "https://facturx.orvel.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"leborgneantoine-facturx": {
"type": "remote",
"url": "https://facturx.orvel.dev/mcp",
"enabled": true
}
}
} openclaw mcp add leborgneantoine-facturx --url 'https://facturx.orvel.dev/mcp' --transport streamable-http
mcp_servers:
leborgneantoine-facturx:
url: "https://facturx.orvel.dev/mcp" {
"McpServers": {
"leborgneantoine-facturx": {
"Transport": "http",
"Url": "https://facturx.orvel.dev/mcp"
}
}
} assistant mcp add leborgneantoine-facturx -t streamable-http -u 'https://facturx.orvel.dev/mcp'
{
"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.
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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 8 Sept 26 +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.
- 6 Sept 26 +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.
- 4 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
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 20 Sept 2026 · Probed https://facturx.orvel.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=facturx.orvel.dev | CN=YR2,O=Let's Encrypt,C=US | 2 Sept 2026 | 1 Dec 2026 | RSA 2048 | SHA256-RSA | 5364264daacaf7cc45a85380c69caad33d5 |
| SANs: facturx.orvel.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of facturx.orvel.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| orvel.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://facturx.orvel.dev/mcp | Verified | 200 | |
| http (plaintext) | http://facturx.orvel.dev/mcp | HTTPS enforced | 301 | https://facturx.orvel.dev/mcp |
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 →
embed_xml Embed Factur-X XML into a PDF ~228
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Your existing visual invoice PDF (any PDF, will be converted to PDF/A-3), base64 encoded |
| xml | string | yes | Factur-X / CII XML text for the same invoice; must pass the `check` rules or the tool fails |
No output schema declared.
No examples provided.
extract_invoice Extract e-invoice data ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
Structured output declared, but exposes no named fields.
No examples provided.
generate_invoice Generate Factur-X invoice ~477
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | yes | 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… |
No output schema declared.
No examples provided.
validate_invoice Validate e-invoice ~246
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
Structured output declared, but exposes no named fields.
No examples provided.
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 83 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.