# VeriFactu (pypi · verifactu-keyflint-mcp)

Audit VERI*FACTU hash chains, build the AEAT tax QR, build and validate Facturae 3.2.2 invoices.

- Trust score: 67/100 (medium)
- Change this week: −8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.keyflint.dev`: 32/100, [markdown](https://verifymcp.io/servers/arceedev-verifactu-mcp/verifactu-mcp.md), [page](https://verifymcp.io/servers/arceedev-verifactu-mcp/verifactu-mcp)
- pypi · `verifactu-keyflint-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/arceedev-verifactu-mcp/verifactu-keyflint-mcp.md), [page](https://verifymcp.io/servers/arceedev-verifactu-mcp/verifactu-keyflint-mcp)

## Channel facts

- Registry: `pypi`
- Package: `verifactu-keyflint-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 2 of 34 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 84/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to ArceeDev/verifactu-mcp).
  - License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license.
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### 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.

### Claude

```bash
claude mcp add arceedev-verifactu-mcp -- uvx verifactu-keyflint-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "arceedev-verifactu-mcp": {
      "command": "uvx",
      "args": [
        "verifactu-keyflint-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "arceedev-verifactu-mcp": {
      "command": "uvx",
      "args": [
        "verifactu-keyflint-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add arceedev-verifactu-mcp -- uvx verifactu-keyflint-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "arceedev-verifactu-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "verifactu-keyflint-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add arceedev-verifactu-mcp --command uvx --arg verifactu-keyflint-mcp
```

### Hermes

```yaml
mcp_servers:
  arceedev-verifactu-mcp:
    command: "uvx"
    args: ["verifactu-keyflint-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "arceedev-verifactu-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "verifactu-keyflint-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add arceedev-verifactu-mcp -t stdio -c uvx -a verifactu-keyflint-mcp
```

### Other

```json
{
  "mcpServers": {
    "arceedev-verifactu-mcp": {
      "command": "uvx",
      "args": [
        "verifactu-keyflint-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 67, +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.

### 2026-11-18 (score 66, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-17 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 65, −10)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.30
- [functional] Package version: 0.1.0 → 0.1.1

### 2026-11-14 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-11 (score 60, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-10 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-08 (score 60, −15)

- [security regression] Malware scan: pass → unverified

## MCP tools (11)

### `verifactu_hash` (~224 tokens)

Compute VeriFactu record hash

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).

Input parameters:

- `previous_huella` (string)
- `record` (object, required)

### `validate_invoice_chain` (~205 tokens)

Validate VeriFactu invoice chain

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.

Input parameters:

- `continues_from` (string)
- `records` (array, required)

### `validate_verifactu_xml` (~126 tokens)

Validate VeriFactu XML

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.

Input parameters:

- `content` (string)
- `content_base64` (string)
- `continues_from` (string)

### `generate_verifactu_qr` (~248 tokens)

Generate VeriFactu QR code

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.

Input parameters:

- `environment` (string)
- `fecha` (string, required)
- `image_format` (string)
- `importe` (string, required)
- `nif` (string, required)
- `numserie` (string, required)
- `size_px` (integer)
- `verifactu` (boolean)

### `build_facturae` (~390 tokens)

Build Facturae e-invoice

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.

Input parameters:

- `invoice` (object, required)

### `validate_facturae` (~123 tokens)

Validate Facturae e-invoice

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.

Input parameters:

- `content` (string)
- `content_base64` (string)

### `check_qr_url` (~40 tokens)

Check VeriFactu QR URL

Check a tax QR URL read from an invoice: official AEAT host, path, parameters and formats. Free.

Input parameters:

- `url` (string, required)

### `validate_nif` (~30 tokens)

Validate Spanish tax ID (NIF)

Check a Spanish NIF / NIE / CIF control character. Free.

Input parameters:

- `nif` (string, required)

### `verifactu_calendar` (~42 tokens)

Show VeriFactu deadlines

Legal deadlines for VERI*FACTU and mandatory B2B e-invoicing in Spain, with sources and what is still
pending publication. Free.

### `pricing` (~20 tokens)

Show tool prices

Credit price of each tool and where to buy credits. Free.

### `credits_balance` (~19 tokens)

Check credit balance

Remaining credits on your KeyFlint license. Free.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/arceedev-verifactu-mcp/verifactu-keyflint-mcp#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 67
- 2026-11-19: 66
- 2026-11-18: 66
- 2026-11-17: 81
- 2026-11-16: 65
- 2026-11-15: 65
- 2026-11-14: 75
- 2026-11-13: 60
- 2026-11-12: 60
- 2026-11-11: 60
- 2026-11-10: 75
- 2026-11-09: 60
- 2026-11-08: 60
- 2026-11-07: 75
- 2026-11-06: 60

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/verifactu-keyflint-mcp/
- Socket report: https://socket.dev/pypi/package/verifactu-keyflint-mcp
- Repository: https://github.com/ArceeDev/verifactu-mcp
- Website: https://mcp.keyflint.dev/
- Changelog RSS feed: https://verifymcp.io/servers/arceedev-verifactu-mcp/verifactu-keyflint-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/arceedev-verifactu-mcp/verifactu-keyflint-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/arceedev-verifactu-mcp/verifactu-keyflint-mcp.json
- HTML version of this page: https://verifymcp.io/servers/arceedev-verifactu-mcp/verifactu-keyflint-mcp
