Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FacturX API

PYPI · FACTURX-MCP

Official MCP server for the FacturX API: dry run, Factur-X conversion, validation, rule lookup.

Available components

−15 this week 63 Trust /100

Last scanned (19 hours ago)

Scores higher than 55% of PyPI servers

Category Documents and Files

Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to facturxapi/sdk). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 9 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 576 tokens (~144/item across 4 items; 4 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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
  • 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 5 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.

What we tested

Checks we ran (14)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

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 SecurityMalware scan not yet available for this package.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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 →

Changelog

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.

  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 63

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed pypi/facturx-mcp@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo facturxapi/sdk
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/facturxapi/sdk/.github/workflows/publish-pypi.yml@refs/heads/main
Rekor log index 3819146773
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:addd789fcf238bcb7f42af087923e5aba4330fd5993c4f8fdd34619b495ea8bd

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~470 tokens

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 →

Tool Tokens
facturx_convert ~144

Final conversion: COSTS 1 invoice of the account quota (refunded by the API when no file is produced). Call it only after facturx_dry_run returned ready=true. Writes factur-x.pdf and factur-x.xml into out_dir and returns their paths, sizes, sha256, the verified target and the idempotency_key. If the call fails without an answer, call again with the SAME idempotency_key: the API will not charge twice.

NameTypeReqDescription
idempotency_key–––
invoiceobjectyes–
out_dirstringyes–
outputstring––
validation_targetstring––

Structured output declared, but exposes no named fields.

No examples provided.

facturx_dry_run ~89

Check a complete ERP invoice JSON WITHOUT producing a file and WITHOUT using quota. Use it first, every time. Returns ready (true only when generationReadiness.status is 'ready'; success=false can still be ready), the readiness detail, request_id and idempotency_key.

NameTypeReqDescription
invoiceobjectyes–
outputstring––
validation_targetstring––

Structured output declared, but exposes no named fields.

No examples provided.

facturx_explain_error ~116

Explain an EN16931 / France 2026 rule (e.g. BR-CO-15), a business term (e.g. BT-1) or an invoice JSON path (e.g. totals.gross): returns the matching invoice fields from the API's public integration contract (JSON path, BT, rule, CII XPath, requirement). Free, no API key needed. API error codes (409/503 …) are not in this public source yet.

NameTypeReqDescription
code_or_rulestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

facturx_validate ~121

Validate an existing Factur-X PDF or CII XML file from the local disk against validation_target (default en16931, the same target as facturx_dry_run and facturx_convert; pass france_2026 to check the invoice is ready for a French PA, plateforme agréée). Returns valid, validationStatus, profile, target and the first errors as reported by the API. Counts 1 invoice of the account quota when the API returns a report.

NameTypeReqDescription
file_pathstringyes–
validation_targetstring––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the FacturX API MCP server?

FacturX API runs locally as a PyPI package, launched with uvx facturx-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · facturx-mcp

# add to Claude Code
claude mcp add com-facturxapi-mcp -- uvx facturx-mcp
Common questions

What is the FacturX API MCP server?

FacturX API is an MCP server listed in the public MCP registry as com.facturxapi/mcp. Official MCP server for the FacturX API: dry run, Factur-X conversion, validation, rule lookup. This page covers its PyPI package (facturx-mcp).

Is the FacturX API MCP server safe to use?

FacturX API scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 FacturX API MCP server expose?

FacturX API exposes 4 tools: facturx_dry_run, facturx_convert, facturx_validate, facturx_explain_error. Their descriptions and schemas cost roughly 470 tokens of context every time the server is loaded.

Is the FacturX API MCP server still maintained?

FacturX API is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the FacturX API MCP server under?

FacturX API declares the MIT 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 FacturX API MCP server?

VerifyMCP ran 14 checks on FacturX API, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about FacturX API: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.