Facture Electronique Fr MCP Server

mcp-facture-electronique-fr PyPI v0.8.2

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server exposing the AFNOR XP Z12-013 APIs for French electronic invoicing (Compatible Solution)

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 34

Each tool and what it can reach — statically extracted from the published source.

  • create_webhooknetwork egress
  • delete_webhooknetwork egress
  • update_webhooknetwork egress
  • check_ppf_annuaire_healthno sensitive capability
  • create_directory_lineno sensitive capability
  • create_routing_codeno sensitive capability
  • delete_directory_lineno sensitive capability
  • get_company_by_id_instanceno sensitive capability
  • get_company_by_sirenno sensitive capability
  • get_directory_lineno sensitive capability
Show 24 more tools ↓
  • get_directory_line_by_codeno sensitive capability
  • get_establishment_by_id_instanceno sensitive capability
  • get_establishment_by_siretno sensitive capability
  • get_flowno sensitive capability
  • get_routing_code_by_id_instanceno sensitive capability
  • get_routing_code_by_siret_and_codeno sensitive capability
  • get_webhookno sensitive capability
  • healthcheck_flowno sensitive capability
  • list_webhooksno sensitive capability
  • replace_directory_lineno sensitive capability
  • replace_routing_codeno sensitive capability
  • search_companyno sensitive capability
  • search_directory_lineno sensitive capability
  • search_establishmentno sensitive capability
  • search_flowsno sensitive capability
  • search_routing_codeno sensitive capability
  • submit_flowno sensitive capability
  • submit_lifecycle_statusno sensitive capability
  • submit_payment_reportno sensitive capability
  • submit_transaction_reportno sensitive capability
  • update_directory_lineno sensitive capability
  • update_routing_codeno sensitive capability
  • validate_ereporting_xmlno sensitive capability
  • validate_facturxno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.8.2 latest A 95/100 0 1.13.0 2026-08-25
v0.8.0 A 95/100 0 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-facture-electronique-fr/badge.svg)](https://mcptrustchecker.com/registry/mcp-facture-electronique-fr)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-facture-electronique-fr"><img src="https://mcptrustchecker.com/registry/mcp-facture-electronique-fr/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-facture-electronique-fr/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-facture-electronique-fr --online --registry pypi

Use the free API → How scoring works

More in Finance & Commerce