# io.github.cmendezs/mcp-cfdi-mx (pypi · mcp-cfdi-mx)

MCP server for Mexican electronic invoicing (CFDI 4.0, Pagos 2.0)

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `mcp-cfdi-mx`: 77/100 (this document), [markdown](https://verifymcp.io/servers/cmendezs-mcp-cfdi-mx/mcp-cfdi-mx.md), [page](https://verifymcp.io/servers/cmendezs-mcp-cfdi-mx/mcp-cfdi-mx)

## Channel facts

- Registry: `pypi`
- Package: `mcp-cfdi-mx`
- Version: `0.4.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-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 2 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 7 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2183 tokens (~363/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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).

## Install

### How do I install the io.github.cmendezs/mcp-cfdi-mx server?

io.github.cmendezs/mcp-cfdi-mx runs locally as a PyPI package, launched with uvx mcp-cfdi-mx. 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 cmendezs-mcp-cfdi-mx -- uvx mcp-cfdi-mx
```

### Cursor

```json
{
  "mcpServers": {
    "cmendezs-mcp-cfdi-mx": {
      "command": "uvx",
      "args": [
        "mcp-cfdi-mx"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cmendezs-mcp-cfdi-mx": {
      "command": "uvx",
      "args": [
        "mcp-cfdi-mx"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cmendezs-mcp-cfdi-mx -- uvx mcp-cfdi-mx
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add cmendezs-mcp-cfdi-mx --command uvx --arg mcp-cfdi-mx
```

### Hermes

```yaml
mcp_servers:
  cmendezs-mcp-cfdi-mx:
    command: "uvx"
    args: ["mcp-cfdi-mx"]
```

### Netclaw

```json
{
  "McpServers": {
    "cmendezs-mcp-cfdi-mx": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-cfdi-mx"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cmendezs-mcp-cfdi-mx -t stdio -c uvx -a mcp-cfdi-mx
```

### Other

```json
{
  "mcpServers": {
    "cmendezs-mcp-cfdi-mx": {
      "command": "uvx",
      "args": [
        "mcp-cfdi-mx"
      ]
    }
  }
}
```

## 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-09-19 (score 77, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-18 (score 61, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 75, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 59, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 73, +15)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.30 → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.4.0 → 0.4.1

### 2026-09-11 (score 58, −15)

- [security regression] Malware scan: pass → unverified

## MCP tools (6)

### `mx__get_supported_scope` (~155 tokens)

Mx  Get Supported Scope

Return the CFDI document types, complementos, and sealing modes this package supports.

Reflects Phase 1 scope: CFDI 4.0 Ingreso + Egreso + Complemento de Pagos
2.0, PAC-agnostic sealing. Build (`mx__build_cfdi`/`mx__build_pago`),
XSD validation (`mx__validate_cfdi`), sealing (`mx__seal_cfdi`), and TFD
verification (`mx__verify_tfd`) are all implemented. PAC submission
transport and later-phase complementos are not.

Returns:
    A `ScopeInfo` describing current scope, for callers to check before
    assuming a document type or complemento is supported.

Output parameters:

- `out_of_scope` (array): Capabilities deliberately not implemented yet
- `phase` (integer): Package's own delivery-phase number
- `schema_version` (string): Wire-format schema version this package targets
- `sealing_modes` (array)
- `supported_complementos` (array)
- `supported_document_types` (array): Document-type codes supported today

### `mx__build_cfdi` (~317 tokens)

Mx  Build Cfdi

Build a well-formed, unsealed CFDI 4.0 `Comprobante` XML (Ingreso or Egreso).

\`comprobante_data` is validated against `CFDIComprobante` — see that
model for the full field list (`seller`/`buyer` as `MXEmisor`/
\`MXReceptor`, `lines` as `CFDIConcepto`, `tipo_de_comprobante`, etc.).
RFC fields are validated via `TaxIdentifier.validate_mx_rfc` as part of
model construction; a malformed RFC is reported as a validation error,
not a generated document.

The output XML omits `Sello`/`NoCertificado`/`Certificado` — those three
schema-required attributes are populated by `mx__seal_cfdi`, run
afterward. `mx__validate_cfdi` run on this output is expected to report
exactly those three attributes missing; that is not a bug in this tool.

For `TipoDeComprobante="P"` (Complemento de Pagos), use `mx__build_pago`
instead — this tool only builds Ingreso/Egreso Comprobantes.

Returns a dict with:
\- ``xml``: the generated, unsealed CFDI 4.0 XML string
\- ``total``: the computed `Total` attribute (SubTotal - Descuento +
  traslados - retenciones)

Input parameters:

- `comprobante_data` (object, required): Fields matching the CFDIComprobante schema (Ingreso or Egreso only)

### `mx__build_pago` (~329 tokens)

Mx  Build Pago

Build a well-formed, unsealed Complemento de Pagos 2.0 CFDI.

Composes the fixed single-`Concepto` wrapper SAT's Guía de llenado de
pagos mandates for a Pago-type `Comprobante` (`ClaveProdServ`,
\`ClaveUnidad`, `Descripcion`, `ValorUnitario`, `Importe`, `ObjetoImp` are
all fixed conventional values — see this module's docstring constants)
with the `Pagos20` complement built from `pagos_data`, and attaches the
complement under `cfdi:Complemento`.

\`buyer.uso_cfdi` is forced to `"CP01"` (the schema requires it for every
Pagos CFDI per the same guide, regardless of what the caller passes) —
mirrors how this tool already forces `SubTotal`/`Moneda`/etc.

The output XML omits `Sello`/`NoCertificado`/`Certificado`, same as
\`mx__build_cfdi` — seal afterward with `mx__seal_cfdi`.

Returns a dict with:
\- ``xml``: the generated, unsealed CFDI XML string (with the Pagos
  complement attached)

Input parameters:

- `comprobante_data` (object, required): Fields matching CFDIComprobante, minus SubTotal/Moneda/FormaPago/MetodoPago/CondicionesDePago/lines/TipoDeComprobante — all fixed or derived for a Pagos CFDI, do not supply them
- `pagos_data` (object, required): Fields matching the Pagos20 schema

### `mx__validate_cfdi` (~335 tokens)

Mx  Validate Cfdi

Validate a CFDI 4.0 document against the official SAT XSD schemas.

Always validates the root `Comprobante` against `cfdv40.xsd`. If a
\`TimbreFiscalDigital` complement is present (i.e. the document has been
stamped by a PAC), it is additionally validated against
\`TimbreFiscalDigitalv11.xsd.xml`. If a `Pagos` complement is present
(`TipoDeComprobante="P"`), it is additionally validated against
\`Pagos20.xsd.xml`.

This is XSD-only — business-rule checks from SAT's Matriz de errores
(`specs/MatrizDeErrores_CFDI_v40_20260325.xls`) are not run, mirroring
\`mcp-nfe-br`'s `br__validate_nfe_xml` precedent (XSD-first, business
rules deferred). A document that passes this validator is structurally
conformant but not guaranteed to pass PAC certification.

Returns a dict with:
\- ``valid``: True only if every schema that applies passed
\- ``comprobante``: the `cfdv40.xsd` validation result
\- ``tfd``: the TFD validation result, present only if a
  \`TimbreFiscalDigital` element was found
\- ``pagos``: the Pagos 2.0 validation result, present only if a
  \`Pagos` element was found

Input parameters:

- `xml` (string, required): The CFDI 4.0 Comprobante XML to validate, as a string

### `mx__seal_cfdi` (~554 tokens)

Mx  Seal Cfdi

Seal (or deliberately not seal) a CFDI 4.0 Comprobante, PAC-agnostic.

\`sealing_mode="local"` computes the cadena original via the actual SAT
XSLT transform (`resources/cadenaoriginal_4_0.xslt`, with its
\`utilerias.xslt` and `Pagos20.xslt` includes resolved from `resources/`;
any other complemento
include a document might reference is not in Phase-1 scope and stubs to
a no-op template — see `SelloDigitalSigner`'s docstring), then computes
\`Sello`/`NoCertificado`/`Certificado` via
\`mcp_einvoicing_core.digital_signature.SelloDigitalSigner` — no local
reimplementation of the signing algorithm.

\`sealing_mode="pac"` returns *xml* unchanged: some PACs accept an
unsealed, schema-valid CFDI and seal it on the emisor's behalf. This
tool does not submit to any PAC — see the package README for the
PAC-agnostic design.

CSD key material is always a file path, never accepted as plaintext key
content in a tool argument.

Returns a dict with:
\- ``xml``: the sealed (or, for ``"pac"``, unchanged) XML string
\- ``sealing_mode``: echoes the mode used

Input parameters:

- `cert_path`: Path to the CSD's DER-encoded certificate (.cer). Required when sealing_mode='local'.
- `key_password`: Passphrase for the private key. Required when sealing_mode='local'. This is a secret that transits the tool call as plain text — callers should source it from an environment variable or secrets manag…
- `key_path`: Path to the CSD's encrypted PKCS#8 DER private key (.key). Required when sealing_mode='local'.
- `no_certificado`: The CSD's 20-digit serial number from the SAT enrollment acknowledgment (acuse). Not derived from the certificate bytes — no confirmed algorithm exists for that derivation, see SelloDigitalSigner's d…
- `sealing_mode` (string, required): 'local': compute Sello/NoCertificado/Certificado from the supplied CSD. 'pac': return the XML unchanged, for a PAC that seals on the emisor's behalf.
- `xml` (string, required): The unsealed CFDI 4.0 Comprobante XML, as returned by mx__build_cfdi/mx__build_pago

### `mx__verify_tfd` (~369 tokens)

Mx  Verify Tfd

Parse a Timbre Fiscal Digital 1.1 stamp and, optionally, verify SelloSAT.

Always returns the TFD's own attributes (`UUID`, `FechaTimbrado`,
\`RfcProvCertif`, `SelloCFD`, `NoCertificadoSAT`, `SelloSAT`, ...) and the
recomputed cadena original (via `cadenaoriginal_TFD_1_1.xslt`, per
Anexo 20 Rubro III.B). If `pac_certificado_der_b64` is supplied,
additionally verifies `SelloSAT` (SHA-256 + RSA-PKCS#1v1.5, the same
algorithm as the emisor's own Sello) against that certificate's public
key. Without it, `sello_sat_verified` is `null` — parsing succeeded but
cryptographic verification was not attempted, not "passed".

Returns a dict with:
\- ``found``: False if no `TimbreFiscalDigital` element exists in *xml*
\- ``fields``: the TFD's own attributes
\- ``cadena_original``: the recomputed cadena original string
\- ``sello_sat_verified``: True/False if `pac_certificado_der_b64` was
  supplied, else null

Input parameters:

- `pac_certificado_der_b64`: Base64-encoded DER certificate of the PAC/SAT that stamped this TFD, used to cryptographically verify SelloSAT. SAT does not embed this certificate in the TFD itself, so it is not available without t…
- `xml` (string, required): The sealed, PAC-stamped CFDI XML (with a TimbreFiscalDigital complement)

## Diagnostics

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

## Score history

- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 61
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 59
- 2026-09-13: 74
- 2026-09-12: 73
- 2026-09-11: 58
- 2026-09-10: 73
- 2026-09-09: 72
- 2026-09-08: 72
- 2026-09-07: 71
- 2026-09-06: 71
- 2026-09-05: 70
- 2026-09-04: 70
- 2026-09-03: 63
- 2026-09-02: 48

## Common questions

### What is the io.github.cmendezs/mcp-cfdi-mx server?

io.github.cmendezs/mcp-cfdi-mx is listed in the public MCP registry as io.github.cmendezs/mcp-cfdi-mx. MCP server for Mexican electronic invoicing (CFDI 4.0, Pagos 2.0). This page covers its PyPI package (mcp-cfdi-mx).

### Is the io.github.cmendezs/mcp-cfdi-mx server safe to use?

io.github.cmendezs/mcp-cfdi-mx scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.cmendezs/mcp-cfdi-mx server expose?

io.github.cmendezs/mcp-cfdi-mx exposes 6 tools: mx__get_supported_scope, mx__build_cfdi, mx__build_pago, mx__validate_cfdi, mx__seal_cfdi, mx__verify_tfd. Their descriptions and schemas cost roughly 2,059 tokens of context every time the server is loaded.

### Is the io.github.cmendezs/mcp-cfdi-mx server still maintained?

io.github.cmendezs/mcp-cfdi-mx is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.cmendezs/mcp-cfdi-mx server under?

io.github.cmendezs/mcp-cfdi-mx declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/mcp-cfdi-mx/
- Socket report: https://socket.dev/pypi/package/mcp-cfdi-mx
- Repository: https://github.com/cmendezs/mcp-cfdi-mx
- Changelog RSS feed: https://verifymcp.io/servers/cmendezs-mcp-cfdi-mx/mcp-cfdi-mx.xml
- Changelog JSON feed: https://verifymcp.io/servers/cmendezs-mcp-cfdi-mx/mcp-cfdi-mx.json
- HTML version of this page: https://verifymcp.io/servers/cmendezs-mcp-cfdi-mx/mcp-cfdi-mx