MaFactureOK
REMOTE · MAFACTUREOK.COM
Vérifie une facture électronique (Factur-X, UBL, CII), un SIREN/SIRET, une TVA ; explique un rejet.
Available components
Last scanned (18 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 813 tokens (~162/item across 5 items; 4 tools + 1 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 Management40
- Stability observed for 12 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
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
- Supports UI / widget rendering.Pass
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 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 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.
- 13 Oct 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.
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 10 Oct 26 74
First indexed and scored.
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 22 Oct 2026 · Probed https://mafactureok.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mafactureok.com | CN=WR3,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | RSA 2048 | SHA256-RSA | 95979cc0e70673ee10ce545691af666b |
| SANs: mafactureok.com, *.mafactureok.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mafactureok.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mafactureok.com. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://static.cloudflareinsights.com https://analytics.ahrefs.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://*.google-analytics.com https://*.googletagmanager.com; font-src 'self'; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://cloudflareinsights.com https://analytics.ahrefs.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mafactureok.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://mafactureok.com/api/mcp | HTTPS enforced | 301 | https://mafactureok.com:443/api/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 →
expliquer_code_rejet Expliquer un code de rejet ou une règle de validation ~134
Traduit en clair un motif de rejet ou de refus de facture électronique (codes AFNOR XP Z12-012 : REJ_SEMAN, REJ_ADR, DEST_INC, NON_TRANSMISE, TX_TVA_ERR…) ou une règle de validation EN 16931 / française (BR-CO-15, BR-FR-10, BR-S-08…) : signification, action attendue, faut-il un avoir. Sans clé, données du site MaFactureOK.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Code tel que reçu, par exemple REJ_SEMAN ou BR-CO-15 |
No output schema declared.
No examples provided.
valider_facture Vérifier une facture électronique (dépôt de fichier) ~141
Ouvre une carte de dépôt dans la conversation. L'utilisateur y glisse sa facture électronique (PDF Factur-X, XML UBL ou CII, 15 Mo au maximum) ; le fichier est envoyé directement à MaFactureOK, analysé puis effacé, et la carte affiche le verdict (valide, à vérifier, invalide), chaque anomalie en français avec la correction attendue, et l'état des entreprises de la facture au registre officiel. À appeler dès que l'utilisateur veut vérifier, valider ou comprendre le rejet d'une facture qu'il possède en fichier. Aucun argument : le fichier n'est jamais transmis par le modèle.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verifier_tiers Vérifier une entreprise (SIREN ou SIRET) ~143
Vérifie un ou plusieurs SIREN (9 chiffres) ou SIRET (14 chiffres) au registre officiel des entreprises et auprès de VIES : existe-t-elle, est-elle active ou cessée, sous quel nom et à quelle adresse, son numéro de TVA est-il valide. À utiliser avant de payer une facture ou de créer un client. Sans clé : 5 identifiants par appel, 30 par jour. Avec une clé gratuite (https://mafactureok.com/api) : 25 par appel, 200 par jour.
| Name | Type | Req | Description |
|---|---|---|---|
| identifiants | array | yes | SIREN ou SIRET, espaces et points tolérés |
No output schema declared.
No examples provided.
verifier_tva Vérifier un numéro de TVA intracommunautaire français ~112
Vérifie un numéro de TVA intracommunautaire français (FR + 2 caractères + 9 chiffres) : clé de contrôle, validité auprès du service européen VIES, et entreprise associée au registre officiel (nom, adresse, active ou cessée). Numéros français uniquement ; pour un autre pays, utiliser VIES directement. Sans clé : quota réduit ; clé gratuite facultative.
| Name | Type | Req | Description |
|---|---|---|---|
| numero | string | yes | Numéro de TVA, par exemple FR42456500537 ; espaces tolérés |
No output schema declared.
No examples provided.
How do I install the MaFactureOK MCP server?
MaFactureOK is a hosted endpoint at https://mafactureok.com/api/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 · mafactureok.com
claude mcp add --transport http com-mafactureok-mafactureok 'https://mafactureok.com/api/mcp'
What is the MaFactureOK MCP server?
MaFactureOK is an MCP server listed in the public MCP registry as com.mafactureok/mafactureok. Vérifie une facture électronique (Factur-X, UBL, CII), un SIREN/SIRET, une TVA ; explique un rejet. This page covers its hosted endpoint (https://mafactureok.com/api/mcp).
Is the MaFactureOK MCP server safe to use?
MaFactureOK scores 80 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 MaFactureOK MCP server expose?
MaFactureOK exposes 4 tools: verifier_tiers, verifier_tva, valider_facture, expliquer_code_rejet. Their descriptions and schemas cost roughly 530 tokens of context every time the server is loaded.
Does the MaFactureOK MCP server require authentication?
No. We connected to MaFactureOK without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MaFactureOK MCP server still maintained?
MaFactureOK is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.