VeriFactu
PYPI · VERIFACTU-KEYFLINT-MCP · 2 COMPONENTS
Audit VERI*FACTU hash chains, build the AEAT tax QR, build and validate Facturae 3.2.2 invoices.
Available components
Last scanned (11 hours ago)
Scores higher than 60% of PyPI 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 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
- 2 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ArceeDev/verifactu-mcp). View diagnostics → Pass
- License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- 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 1754 tokens (~146/item across 12 items; 11 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
- Supports UI / widget rendering.Pass
Checks we ran (16)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Checks we could not complete (1)
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.
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 15 Nov 26 −10
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.30 ▲ functional
- Package version: 0.1.0 → 0.1.1 functional
- 14 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 10 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 8 Nov 26 −15
- Malware scan: pass → unverified ▼ security
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/verifactu-keyflint-mcp@0.1.1
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 | ArceeDev/verifactu-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ArceeDev/verifactu-mcp/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 3906623591 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:62d0829ff2cb4aa7bad96e284c36685cf8f370af40203677178124033a0b2be2 |
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 34 packages
| Packages resolved | 34 |
|---|---|
| No linked repository | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
build_facturae Build Facturae e-invoice ~390
Build a Facturae 3.2.2 invoice (XML) from plain data, with totals computed and the official XSD checked. invoice: number (max 20), series, issue_date, operation_date?, currency (EUR), description?, notes?, legal_literals? [text], receiver_contract_reference?, seller / buyer: nif, name (company name, or first name with first_surname/second_surname for a person), address, post_code, town, province, country (ISO alfa-3, default ESP), residence? (R/U/E), email?, phone?; buyer.face: {oficina_contable, organo_gestor, unidad_tramitadora, organo_proponente?} DIR3 codes for public administration invoices (FACe), or administrative_centres: [{code, role 01-04, name?}], lines: [{description, quantity, unit_price, tax_rate (21, 10, 4, 0...), discount_pct?, surcharge_rate? (recargo de equivalencia 5.2, 1.4, 0.5), tax_type? (01 IVA, 03 IGIC, 02 IPSI), unit? (01 unidades), receiver_reference?, file_reference?, article_code?}], withholding?: {rate} (IRPF retention, e.g. 15 or 7), payment?: {due_date, method (transferencia, domiciliacion, efectivo, tarjeta...), iban, bic?}. Amounts accept "1.234,56" or "1234.56". Returns `xml` (UTF-8, unsigned), `xml_base64`, `totals` and the validation report. Invalid data is refused before charging. Sign the XML (XAdES) before sending to FACe.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
check_qr_url Check VeriFactu QR URL ~40
Check a tax QR URL read from an invoice: official AEAT host, path, parameters and formats. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
credits_balance Check credit balance ~19
Remaining credits on your KeyFlint license. Free.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
generate_verifactu_qr Generate VeriFactu QR code ~248
Generate the AEAT tax QR ("QR tributario") of an invoice: URL and image. Args: nif: Issuer NIF. numserie: Invoice series + number exactly as registered. fecha: Issue date (DD-MM-AAAA; AAAA-MM-DD and DD/MM/AAAA are converted). importe: ImporteTotal with decimal point, e.g. "241.40". verifactu: true for VERI*FACTU systems (ValidarQR), false for non-verifiable systems (ValidarQRNoVerifactu). environment: produccion (default) or pruebas (AEAT test portal). size_px: Image width in pixels (100-2000). image_format: png (default) or svg. The image uses error correction level M. `print_rules` says how it must appear on the invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| fecha | string | yes | – |
| image_format | string | – | – |
| importe | string | yes | – |
| nif | string | yes | – |
| numserie | string | yes | – |
| size_px | integer | – | – |
| verifactu | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pricing Show tool prices ~20
Credit price of each tool and where to buy credits. Free.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
validate_facturae Validate Facturae e-invoice ~123
Validate a Facturae 3.2.2 file (.xml or signed .xsig) before sending it to FACe or a client. Checks the official XSD, the arithmetic FACe checks (line amounts, tax quotas, header vs line bases, totals, batch totals, installments), NIFs of resident parties, the three DIR3 codes for public administrations, and whether the file is signed. Files that are not Facturae are not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| content_base64 | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
validate_invoice_chain Validate VeriFactu invoice chain ~205
Audit a VERI*FACTU chain of records (in generation order) given as JSON objects. Each record has the fields of `verifactu_hash` plus `Huella` (stored fingerprint) and optionally `HuellaAnterior` or `RegistroAnterior` {IDEmisorFactura, NumSerieFactura, FechaExpedicionFactura, Huella} and `PrimerRegistro` ("S"). For every record the fingerprint is recomputed and compared, and the link to the previous record checked. Reports chain breaks, altered records, PrimerRegistro misuse, duplicate invoices, cancellations of unknown invoices, timestamps going backwards, invalid NIF/dates/amounts/TipoFactura. continues_from: last fingerprint of the previous batch, to audit a chain in pieces. Up to 20,000 records. `last_huella` is what the next record must link to.
| Name | Type | Req | Description |
|---|---|---|---|
| continues_from | string | – | – |
| records | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
validate_nif Validate Spanish tax ID (NIF) ~30
Check a Spanish NIF / NIE / CIF control character. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| nif | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
validate_verifactu_xml Validate VeriFactu XML ~126
Audit VERI*FACTU XML exported by an invoicing program (RegFactuSistemaFacturacion, a SOAP envelope, or any XML holding RegistroAlta / RegistroAnulacion elements, in document order). Validates RegFactuSistemaFacturacion against the official AEAT schema (SuministroLR.xsd) when present, then runs every chain and fingerprint check of `validate_invoice_chain`. XML that holds no records is not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| content_base64 | string | – | – |
| continues_from | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
verifactu_calendar Show VeriFactu deadlines ~42
Legal deadlines for VERI*FACTU and mandatory B2B e-invoicing in Spain, with sources and what is still pending publication. Free.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
verifactu_hash Compute VeriFactu record hash ~224
Compute the VERI*FACTU fingerprint (huella, SHA-256) of one invoicing record. record (AEAT field names; snake_case aliases accepted): alta: IDEmisorFactura, NumSerieFactura, FechaExpedicionFactura (DD-MM-AAAA), TipoFactura (F1, F2, F3, R1-R5), CuotaTotal, ImporteTotal (as written in the XML, decimal point), FechaHoraHusoGenRegistro (AAAA-MM-DDThh:mm:ss+hh:mm). anulación (TipoRegistro="anulacion"): IDEmisorFacturaAnulada, NumSerieFacturaAnulada, FechaExpedicionFacturaAnulada, FechaHoraHusoGenRegistro. previous_huella: fingerprint of the previous record of the chain; empty for the first record. Returns the fingerprint, the exact string hashed and any field problems (an error means the AEAT would reject the record).
| Name | Type | Req | Description |
|---|---|---|---|
| previous_huella | string | – | – |
| record | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the VeriFactu MCP server?
VeriFactu runs locally as a PyPI package, launched with uvx verifactu-keyflint-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 · verifactu-keyflint-mcp
claude mcp add arceedev-verifactu-mcp -- uvx verifactu-keyflint-mcp
What is the VeriFactu MCP server?
VeriFactu is an MCP server listed in the public MCP registry as io.github.ArceeDev/verifactu-mcp. Audit VERI*FACTU hash chains, build the AEAT tax QR, build and validate Facturae 3.2.2 invoices. This page covers its PyPI package (verifactu-keyflint-mcp).
Is the VeriFactu MCP server safe to use?
VeriFactu scores 67 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 VeriFactu MCP server expose?
VeriFactu exposes 11 tools: verifactu_hash, validate_invoice_chain, validate_verifactu_xml, generate_verifactu_qr, build_facturae, and 6 more. Their descriptions and schemas cost roughly 1,467 tokens of context every time the server is loaded.
Is the VeriFactu MCP server still maintained?
VeriFactu 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 VeriFactu MCP server under?
VeriFactu declares the BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.
What did VerifyMCP test on the VeriFactu MCP server?
VerifyMCP ran 16 checks on VeriFactu, covering Known CVEs, Install scripts, Dependency health, Source repository and 12 more. One item could not be completed, a gap on our side rather than a finding about VeriFactu: Malware scan. 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.