Skip to content
Vérifier ma facture logo

Vérifier ma facture MCP server

Which servers in the official MCP registry are Vérifier ma facture's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Vérifier ma facture

Whose server it is
  • Registry namefr.verifier-ma-facture/validateurverified in the MCP registry

The registry name sits under verifier-ma-facture.fr. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools2
  • Server calls itselfverifier-ma-facture
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 1143 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check a PDF invoice's Factur-X conformity before sending; identify blocking errors in e-invoice files.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "check a PDF invoice's Factur-X conformity before sending", the likely first call is verifier_facture.
  • For "identify blocking errors in e-invoice files", the likely first call is verifier_facture.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer955 ms
  • Space in an agent's context≈ 308 tokensthe definitions of all its tools (2), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · check a PDF invoice's Factur-X conformity before sending
  • can do · identify blocking errors in e-invoice files
  • not sure · validate embedded XML against EN 16931 rules

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-26
  • verifier_facture

    Analyse un PDF de facture et rend un rapport de conformité Factur-X en 21 critères : essentiels (PDF/A-3, XML CII intégré), stricts (règles contrôlées par les plateformes agréées françaises, dont BR-FR-05, BR-FR-08 et BR-FR-CO-05) et…

  • lister_criteres

    Rend la grille complète des critères de conformité Factur-X vérifiés par verifier_facture (essentiels, stricts, avancés), avec les références normatives (EN 16931, ISO 19005-3, règles françaises BR-FR). Utile pour expliquer un rapport ou…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "validateur": {
      "type": "http",
      "url": "https://mcp.verifier-ma-facture.fr/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http verifier-ma-facture https://mcp.verifier-ma-facture.fr/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.verifier-ma-facture.fr/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.