io.github.kOlapsis/gofact
MCPB · GOFACT-MCP_1.2.0_LINUX_AMD64.MCPB · 6 COMPONENTS
Creates compliant French e-invoices locally: Factur-X PDF/A-3 with EN 16931 CII XML, legal numbering
Last scanned (12 hours ago)
Scores higher than 90% of MCPB servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (AGPL-3.0-or-later).Pass
- Actively maintained (last published 60 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 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 2014 tokens (~143/item across 14 items; 14 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 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 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed mcpb/https://github.com/kOlapsis/gofact/releases/download/v1.2.0/gofact-mcp_1.2.0_linux_amd64.mcpb@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
create_invoice ~290
Crée la facture : attribue le numéro (séquence légale, continue), écrit le HTML et les données dans le dossier de l'organisation, génère le PDF Factur-X (PDF/A-3 + XML EN 16931) et inscrit la facture au registre — le tout en une transaction. Avant d'appeler : faire valider le contenu (client, lignes, montants, date) par l'utilisateur, en lui annonçant le numéro via preview_next_number.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | la facture HTML complète et imprimable (A4, CSS embarqué), contenant le jeton {{NUMERO}} à l'emplacement du numéro |
| org | string | – | chemin du dossier de l'organisation ; omis si une seule organisation existe |
| spec | object | yes | les données structurées de la facture (montants en CENTIMES) ; ne pas renseigner number, le serveur l'attribue ; title = objet de la facture (intitulé au registre) ; notes = compléments seulement, le… |
| update_template | boolean | – | true si ce HTML doit devenir le nouveau modèle de référence de l'organisation (changement de mise en page voulu par l'utilisateur) |
| Name | Type | Req | Description |
|---|---|---|---|
| factur_x_conform | boolean | yes | – |
| html_path | string | yes | – |
| number | string | yes | – |
| pdf_path | string | yes | – |
| template_frozen | boolean | – | – |
| total_ht_cents | integer | yes | – |
| total_ttc_cents | integer | yes | – |
| warnings | null|array | – | – |
No examples provided.
find_routing_address ~91
Vérifie dans l'annuaire Peppol qu'un destinataire est adressable électroniquement, et sous quels identifiants. Indispensable avant un envoi PDP : sans adresse de routage valide, le dépôt est rejeté.
| Name | Type | Req | Description |
|---|---|---|---|
| siren | string | yes | SIREN (9 chiffres) ou SIRET (14 chiffres, ramené au SIREN) du destinataire |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| reachable | boolean | yes | – |
| routes | null|array | yes | – |
No examples provided.
get_invoice_status ~90
Cycle de vie d'une facture déjà déposée sur la PDP (fr:200 déposée → fr:201 émise → fr:202 reçue…). Un rejet (fr:213) est signalé avec ses motifs, règle par règle.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | numéro de la facture |
| org | string | – | chemin du dossier de l'organisation ; omis si une seule organisation existe |
| Name | Type | Req | Description |
|---|---|---|---|
| events | null|array | yes | – |
| provider | string | yes | – |
| reasons | null|array | – | – |
| rejected | boolean | yes | – |
No examples provided.
get_invoice_template ~132
Modèle HTML de référence de l'organisation, figé lors de la première facture. TOUJOURS l'appeler avant de composer une facture, et REPARTIR DU HTML renvoyé (mêmes classes, même structure, même feuille de style) : les factures d'une même entité doivent se ressembler. Tant qu'aucun modèle n'est figé, l'outil renvoie le modèle par défaut de gofact (is_default) — jamais rien, donc jamais de page blanche.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | – | chemin du dossier de l'organisation ; omis si une seule organisation existe |
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | – | – |
| is_default | boolean | – | – |
| note | string | yes | – |
No examples provided.
get_organization ~70
Fiche d'une organisation : identité de l'émetteur (jamais de secret ni d'IBAN en clair), état de la numérotation, présence du modèle de facture figé.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | – | chemin du dossier de l'organisation ; omis si une seule organisation existe |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| city | string | – | – |
| country | string | – | – |
| string | – | – | |
| has_iban | boolean | yes | – |
| has_pdp | boolean | yes | – |
| has_template | boolean | yes | – |
| invoices | integer | yes | – |
| name | string | yes | – |
| next_number | string | yes | – |
| path | string | yes | – |
| postal_code | string | – | – |
| siren | string | – | – |
| siret | string | – | – |
No examples provided.
init_organization ~282
Crée un dossier d'organisation : registre de numérotation et identité de l'émetteur. Refuse d'écraser un dossier existant. Demander les informations à l'utilisateur, ne jamais les inventer — et TOUJOURS demander si des factures ont déjà été émises cette année : si oui, last_invoice_number reprend la séquence là où elle en est.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | adresse (rue) |
| city | string | – | – |
| string | – | – | |
| iban | string | – | IBAN de règlement — requis pour émettre des factures payables par virement |
| last_invoice_number | string | – | dernier numéro déjà émis (ex. 2026011) si l'utilisateur facturait déjà avant gofact — TOUJOURS poser la question : la numérotation doit continuer sans trou ni doublon |
| name | string | yes | nom de l'entité émettrice |
| path | string | yes | dossier à créer pour l'organisation |
| postal_code | string | – | – |
| siren | string | – | SIREN (9 chiffres), si pas de SIRET |
| siret | string | – | SIRET (14 chiffres) |
| vat_number | string | – | n° TVA intracommunautaire ; vide en franchise 293 B |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| city | string | – | – |
| country | string | – | – |
| string | – | – | |
| has_iban | boolean | yes | – |
| has_pdp | boolean | yes | – |
| has_template | boolean | yes | – |
| invoices | integer | yes | – |
| name | string | yes | – |
| next_number | string | yes | – |
| path | string | yes | – |
| postal_code | string | – | – |
| siren | string | – | – |
| siret | string | – | – |
No examples provided.
initialize_numbering ~128
Reprend une numérotation existante quand l'utilisateur facturait déjà avant gofact : le compteur de l'année passe au dernier numéro émis, le suivant sera émis par gofact. Le compteur ne peut que monter — l'abaisser réutiliserait des numéros, ce qui est interdit. Idempotent.
| Name | Type | Req | Description |
|---|---|---|---|
| last_invoice_number | string | yes | dernier numéro déjà émis (ex. 2026011) — le prochain émis sera le suivant |
| org | string | – | chemin du dossier de l'organisation ; omis si une seule organisation existe |
| Name | Type | Req | Description |
|---|---|---|---|
| next_number | string | yes | – |
No examples provided.
list_invoices ~102
Factures inscrites au registre de l'organisation, de la plus récente à la plus ancienne.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | filtrer par nom de client (sous-chaîne) |
| limit | integer | – | nombre maximal d'entrées (défaut 20) |
| org | string | – | chemin du dossier de l'organisation ; omis si une seule organisation existe |
| year | string | – | filtrer par année d'émission (YYYY) |
| Name | Type | Req | Description |
|---|---|---|---|
| invoices | null|array | yes | – |
No examples provided.
list_organizations ~46
Liste les organisations (entités émettrices de factures) configurées sur ce poste, avec leur identité publique, leur compteur et leur prochain numéro. À appeler en premier.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| organizations | null|array | yes | – |
No examples provided.
preview_invoice ~120
Rend un HTML de facture en PDF d'aperçu, SANS rien consommer ni enregistrer : ni numéro, ni registre, ni Factur-X. L'outil de mise au point du modèle — montrer le PDF à l'utilisateur, recueillir ses retours, itérer, et seulement ensuite create_invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | le HTML de la facture ou du modèle à prévisualiser (avec le jeton {{NUMERO}}) |
| org | string | – | chemin du dossier de l'organisation ; omis si une seule organisation existe |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| pdf_path | string | yes | – |
No examples provided.
preview_next_number ~63
Prochain numéro de facture, SANS le consommer — pour l'annoncer à l'utilisateur avant confirmation. Seul create_invoice attribue réellement le numéro.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | – | chemin du dossier de l'organisation ; omis si une seule organisation existe |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| number | string | yes | – |
No examples provided.
search_client ~140
Recherche un client : d'abord l'historique de facturation de l'organisation (coordonnées validées par l'usage — TOUJOURS les réutiliser), puis, si l'historique ne connaît pas le nom, l'annuaire public des entreprises (SIRENE) pour résoudre nom, SIREN, SIRET et adresse du siège. Ne retenir qu'un candidat actif, confirmé par l'utilisateur.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | – | chemin du dossier de l'organisation ; omis si une seule organisation existe |
| query | string | yes | nom (sous-chaîne), SIREN ou SIRET du client recherché |
| Name | Type | Req | Description |
|---|---|---|---|
| directory | null|array | – | – |
| known_clients | null|array | yes | – |
| note | string | – | – |
No examples provided.
send_invoice ~163
Dépose une facture émise sur la plateforme de dématérialisation (PDP) de l'organisation. IRRÉVERSIBLE : la facture entre dans le circuit de la facturation électronique. N'appeler qu'après un accord explicite de l'utilisateur, avec confirm=true. Refuse un acheteur sans adresse de routage connue de l'annuaire, et remonte immédiatement un rejet de la plateforme avec ses motifs.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | doit valoir true, après confirmation EXPLICITE de l'utilisateur — un dépôt PDP est irréversible |
| number | string | yes | numéro de la facture à déposer (ex. 2026007) |
| org | string | – | chemin du dossier de l'organisation ; omis si une seule organisation existe |
| Name | Type | Req | Description |
|---|---|---|---|
| events | null|array | yes | – |
| provider | string | yes | – |
| reasons | null|array | – | – |
| reference | string | yes | – |
| rejected | boolean | yes | – |
No examples provided.
update_organization ~297
Corrige l'identité d'une organisation existante : nom, SIRET, adresse, n° de TVA, IBAN. À utiliser dès qu'une facture est refusée faute d'une donnée de l'émetteur — un IBAN manquant fait échouer BR-50 à la dernière étape. Seuls les champs fournis sont modifiés ; les autres, y compris les identifiants de plateforme, sont conservés intacts. Une chaîne vide efface le champ. Demander les valeurs à l'utilisateur, ne jamais les inventer.
| Name | Type | Req | Description |
|---|---|---|---|
| address | null|string | – | adresse (rue) |
| city | null|string | – | – |
| country | null|string | – | code pays ISO à deux lettres ; FR par défaut |
| null|string | – | – | |
| iban | null|string | – | IBAN de règlement — requis pour une facture payable par virement (BR-50) |
| name | null|string | – | nom de l'entité émettrice |
| org | string | – | chemin du dossier de l'organisation ; omis si une seule organisation existe |
| postal_code | null|string | – | – |
| siren | null|string | – | SIREN (9 chiffres) |
| siret | null|string | – | SIRET (14 chiffres) |
| vat_number | null|string | – | n° TVA intracommunautaire ; chaîne vide pour revenir à la franchise 293 B |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| city | string | – | – |
| country | string | – | – |
| string | – | – | |
| has_iban | boolean | yes | – |
| has_pdp | boolean | yes | – |
| has_template | boolean | yes | – |
| invoices | integer | yes | – |
| name | string | yes | – |
| next_number | string | yes | – |
| path | string | yes | – |
| postal_code | string | – | – |
| siren | string | – | – |
| siret | string | – | – |
No examples provided.
How do I install the io.github.kOlapsis/gofact MCP server?
io.github.kOlapsis/gofact ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · gofact-mcp_1.2.0_linux_amd64.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
What is the io.github.kOlapsis/gofact MCP server?
io.github.kOlapsis/gofact is an MCP server listed in the public MCP registry as io.github.kOlapsis/gofact. Creates compliant French e-invoices locally: Factur-X PDF/A-3 with EN 16931 CII XML, legal numbering. This page covers its MCPB bundle (https://github.com/kOlapsis/gofact/releases/download/v1.2.0/gofact-mcp_1.2.0_linux_amd64.mcpb).
Is the io.github.kOlapsis/gofact MCP server safe to use?
io.github.kOlapsis/gofact scores 56 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 io.github.kOlapsis/gofact MCP server expose?
io.github.kOlapsis/gofact exposes 14 tools: create_invoice, find_routing_address, get_invoice_status, get_invoice_template, get_organization, and 9 more. Their descriptions and schemas cost roughly 2,014 tokens of context every time the server is loaded.
What licence is the io.github.kOlapsis/gofact MCP server under?
io.github.kOlapsis/gofact declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.kOlapsis/gofact MCP server?
VerifyMCP ran 12 checks on io.github.kOlapsis/gofact, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.kOlapsis/gofact: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.