verifier-ma-facture
https://mcp.verifier-ma-facture.fr
Registry code: 3d53fa1747ed86d8
Validateur gratuit de conformité Factur-X pour la réforme française de la facturation électronique. Passez un PDF de facture en base64 à l'outil verifier_facture pour obtenir le rapport complet (21 critères : PDF/A-3, XML CII EN 16931, règles françaises BR-FR). L'outil lister_criteres explique la grille sans fournir de facture. Analyse locale et éphémère : aucune donnée stockée. Édité par SWIPIFY (swipify.fr).
- endpoint
- https://mcp.verifier-ma-facture.fr/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is verifier-ma-facture live?
- Yes — it answered the hub's last check (checked 45m ago). It answered 99% of checks over the last 30 days.
- Is verifier-ma-facture free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does verifier-ma-facture have?
- 2 tools: verifier_facture, lister_criteres.
- Is verifier-ma-facture safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.7%· all time 98.7%
last good check
of 2 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· fetch failed
- down → live
- used for
- validate a factur-x invoice pdf
- list factur-x compliance criteria
- takes → gives
- documents → data
- tools
- 2 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
lister_criteres reads open 11h ago
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 préparer une facture conforme.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesverifier_facture reads unknown 11h ago
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 avancés (qualité). Fournir le PDF encodé en base64 (10 Mo maximum). L'analyse est locale et éphémère : la facture n'est ni stockée ni transmise à un tiers.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "pdf_base64" ], "properties": { "pdf_base64": { "type": "string", "minLength": 1, "description": "Le fichier PDF de la facture, encodé en base64 (avec ou sans préfixe data:)" }, "nom_fichier": { "type": "string", "maxLength": 255, "description": "Nom du fichier, pour l'affichage du rapport (optionnel)" } } }arguments 19 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id3d53fa1747ed86d8.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/3d53fa1747ed86d8/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/3d53fa1747ed86d8?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.