Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing

REMOTE · FACTURLINT.COM

Stateless Factur-X 1.09.2, EN 16931 & French BR-FR-CTC invoice validation and PDF/A-3b auto-repair.

Available components

64 Trust /100

Last scanned (15 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1322 tokens (~120/item across 11 items; 11 tools + 0 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 91% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +4
    • HTTPS: unverified → pass ▲ security
    • Schema quality: 914 → 1322 ▼ functional
    • New tool “convert_stripe_invoice_to_einvoice” functional
    • New tool “extract_accounting_datev” functional
    • New tool “verify_eu_vat_number” functional
  • 19 Nov 26 0
    • Tool “validate_facturx” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 94% ▼ functional
    • Schema quality: pass → fail ▼ functional
    • New tool “convert_invoice_format” functional
    • New tool “extract_accounting_fec” functional
    • New tool “generate_facturx_invoice” functional
    • New tool “parse_visual_pdf_invoice” functional
    • New tool “verify_french_company” functional
    • “validate_facturx” reworded the description of “content_base64” cosmetic
    • “validate_facturx” reworded the description of “filename” cosmetic
  • 18 Nov 26 +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.

  • 17 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 59

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://facturlint.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=facturlint.com CN=YE1,O=Let's Encrypt,C=US 15 Nov 2026 13 Feb 2027 ECDSA 256 ECDSA-SHA384 5649218f7d28b84f87b2341b08202920646
SANs: *.facturlint.com, facturlint.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of facturlint.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
facturlint.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://facturlint.com/mcp Verified 200
http (plaintext) http://facturlint.com/mcp HTTPS enforced 301 https://facturlint.com/mcp
MCP tools · 11 exposed · ~1,322 tokens

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 →

Tool Tokens
convert_invoice_format ~133

Action payante / authentifiée : convertit un fichier XML UBL 2.1, XML CII ou PDF Factur-X en PDF A4 lisible scellé Factur-X (facturx_pdf), en XML CII (cii_xml) ou en XML UBL 2.1 (ubl_xml).

NameTypeReqDescription
content_base64stringyesContenu binaire du fichier XML ou PDF encodé en Base64.
filenamestring–Nom optionnel du fichier source.
target_formatstring–Format de sortie souhaité (par défaut : facturx_pdf).

No output schema declared.

No examples provided.

convert_stripe_invoice_to_einvoice ~165

Action payante / authentifiée : transforme un payload JSON Stripe (événement invoice.finalized ou objet invoice) en facture électronique certifiée Factur-X 1.09.2, ZUGFeRD 2.5 ou XRechnung 3.0 (PDF/A-3b + XML validé).

NameTypeReqDescription
seller_configobject–Paramètres vendeur (seller_name, seller_country, seller_legal_id, seller_vat, seller_iban). Optionnel si un Stripe Bridge est configuré sur la clé API.
stripe_invoiceobjectyesÉvénement Stripe invoice.finalized ou objet Stripe Invoice JSON.
target_profilestring–Profil cible (facturx-en16931 par défaut, ou auto-eu).

No output schema declared.

No examples provided.

explain_facturx_rule ~78

Explique une règle normative Factur-X / EN 16931 / BR-FR-CTC ou PDF/A-3 et fournit un exemple XML correct.

NameTypeReqDescription
codestringyesCode d'erreur (ex: BR-CO-15, BR-FR-04, PDFA3-FX-NS-INVALID).

No output schema declared.

No examples provided.

extract_accounting_datev ~142

Action payante / authentifiée : génère un export comptable allemand DATEV Buchungsstapel CSV (SKR03 ou SKR04, encodage UTF-8 BOM) avec codes TVA BU-Schlüssel depuis une facture Factur-X, ZUGFeRD, XRechnung ou UBL 2.1.

NameTypeReqDescription
content_base64stringyesContenu binaire du PDF Factur-X/ZUGFeRD ou XML CII/UBL encodé en Base64.
filenamestring––
skrstring–Plan comptable allemand DATEV (SKR03 par défaut ou SKR04).

No output schema declared.

No examples provided.

extract_accounting_fec ~139

Action payante / authentifiée : génère des écritures comptables équilibrées Débit = Crédit au format officiel FEC DGFiP (18 colonnes) ou CSV Sage/Cegid depuis une facture Factur-X ou UBL 2.1.

NameTypeReqDescription
content_base64stringyesContenu binaire du PDF Factur-X ou XML CII/UBL encodé en Base64.
export_formatstring–Format d'export (fec DGFiP ou sage_csv).
filenamestring––
journal_typestring–Type de journal comptable (achats ou ventes).

No output schema declared.

No examples provided.

generate_facturx_invoice ~122

Action payante / authentifiée : génère une facture PDF/A-3b Factur-X 1.09.2 EN 16931 & BR-FR-CTC certifiée conforme à partir de données JSON structurées (avec PDF visuel optionnel en Base64).

NameTypeReqDescription
invoice_dataobjectyesObjet JSON conforme au schéma GenerateFacturxRequest.
visual_pdf_base64string–Optionnel : PDF visuel A4 existant encodé en Base64 dans lequel embarquer le XML Factur-X.

No output schema declared.

No examples provided.

parse_visual_pdf_invoice ~100

Outil gratuit : extrait localement (en RAM, sans stockage) les identifiants (SIREN, SIRET, IBAN), numéro, date et montants HT/TVA/TTC d'un PDF classique pour préparer une facture Factur-X.

NameTypeReqDescription
filenamestring–Nom optionnel du fichier PDF.
pdf_base64stringyesContenu binaire du PDF visuel encodé en Base64.

No output schema declared.

No examples provided.

repair_facturx_envelope ~79

Action payante / authentifiée : répare automatiquement l'enveloppe technique PDF/A-3b, le flux XMP Factur-X et l'ICC sRGB sans jamais modifier les montants comptables.

NameTypeReqDescription
pdf_base64stringyesFichier PDF Factur-X défectueux encodé en Base64.

No output schema declared.

No examples provided.

validate_facturx ~150

Valide de manière 100 % déterministe (sans stockage) une facture Factur-X 1.09.2 (PDF/A-3b ou XML CII) ou OASIS UBL 2.1 / Peppol BIS 3.0 contre les schémas officiels EN 16931 et les règles françaises BR-FR-CTC.

NameTypeReqDescription
content_base64stringyesContenu binaire du fichier PDF Factur-X, XML CII ou XML UBL 2.1 encodé en Base64.
filenamestring–Nom optionnel du fichier (ex: facture.pdf, factur-x.xml ou invoice_ubl.xml).

No output schema declared.

No examples provided.

verify_eu_vat_number ~101

Outil gratuit : valide la syntaxe, la clé mathématique (27 États membres UE + XI), le schéma Peppol EAS et interroge en direct le registre officiel européen VIES pour un numéro de TVA intracommunautaire.

NameTypeReqDescription
vat_numberstringyesNuméro de TVA intracommunautaire UE (ex: DE136695976, FR44732829320, BE0403170701).

No output schema declared.

No examples provided.

verify_french_company ~113

Outil gratuit : vérifie un SIREN (9 chiffres), SIRET (14 chiffres), n° de TVA FR ou nom d'entreprise (contrôle de clé de Luhn INSEE, calcul automatique du n° de TVA intracommunautaire FRxx et interrogation en direct du registre officiel INSEE / DGFiP pour vérifier si l'entreprise est active ou cessée).

NameTypeReqDescription
querystringyesSIREN, SIRET, numéro de TVA FR ou raison sociale à vérifier.

No output schema declared.

No examples provided.

Install

How do I install the FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing MCP server?

FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing is a hosted endpoint at https://facturlint.com/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 · facturlint.com

# add to Claude Code
claude mcp add --transport http com-facturlint-facturlint 'https://facturlint.com/mcp'
Common questions

What is the FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing MCP server?

FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing is an MCP server listed in the public MCP registry as com.facturlint/facturlint. Stateless Factur-X 1.09.2, EN 16931 & French BR-FR-CTC invoice validation and PDF/A-3b auto-repair. This page covers its hosted endpoint (https://facturlint.com/mcp).

Is the FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing MCP server safe to use?

FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing scores 64 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 FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing MCP server expose?

FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing exposes 11 tools: validate_facturx, explain_facturx_rule, verify_french_company, repair_facturx_envelope, generate_facturx_invoice, and 6 more. Their descriptions and schemas cost roughly 1,322 tokens of context every time the server is loaded.

Does the FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing MCP server require authentication?

No. We connected to FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing MCP server still maintained?

FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing MCP server?

VerifyMCP ran 12 checks on FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.