# Fiscalisto API docs (remote · fiscalisto.com)

Docs for Fiscalisto's Mexican e-invoicing API (CFDI 4.0): search, operations, SDK code, errors.

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

## Components

- remote · `fiscalisto.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-fiscalisto-docs/docs-api-mcp.md), [page](https://verifymcp.io/servers/com-fiscalisto-docs/docs-api-mcp)

## Channel facts

- Endpoint: `https://fiscalisto.com/docs/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-05.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 990 tokens (~110/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Fiscalisto API docs MCP server?

Fiscalisto API docs is a hosted endpoint at https://fiscalisto.com/docs/api/mcp, so there is nothing to install locally. 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 --transport http com-fiscalisto-docs 'https://fiscalisto.com/docs/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-fiscalisto-docs": {
      "url": "https://fiscalisto.com/docs/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-fiscalisto-docs": {
      "type": "http",
      "url": "https://fiscalisto.com/docs/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-fiscalisto-docs]
url = "https://fiscalisto.com/docs/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-fiscalisto-docs": {
      "type": "remote",
      "url": "https://fiscalisto.com/docs/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-fiscalisto-docs --url 'https://fiscalisto.com/docs/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-fiscalisto-docs:
    url: "https://fiscalisto.com/docs/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-fiscalisto-docs": {
      "Transport": "http",
      "Url": "https://fiscalisto.com/docs/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-fiscalisto-docs -t streamable-http -u 'https://fiscalisto.com/docs/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-fiscalisto-docs": {
      "type": "http",
      "url": "https://fiscalisto.com/docs/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-04 (score 73, +1)

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

### 2026-11-02 (score 72, +1)

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

### 2026-10-31 (score 71, +1)

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

### 2026-10-29 (score 70, +1)

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

### 2026-10-28 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 69)

First indexed and scored.

## MCP tools (9)

### `get_started` (~92 tokens)

Cómo integrar Fiscalisto

Start here when asked to add Fiscalisto or Mexican invoicing (CFDI 4.0) to an app. Empiece aquí: cómo integrar la API en una app de principio a fin (llave, SDK de su lenguaje, timbrar con Idempotency-Key, datos del cliente, errores del SAT, webhooks firmados, cancelar, probar sin costo y pasar a producción), en una página.

### `search_docs` (~94 tokens)

Buscar en la documentación

Busca en la documentación de la API de facturación de Fiscalisto (guías y referencia) y devuelve las páginas que más coinciden. Entiende español e inglés («cancelar factura», «verify webhook signature»). Úsela antes de escribir código contra la API.

Input parameters:

- `query` (string, required): Palabras a buscar, en español o inglés, por ejemplo «cancelar factura motivo 02» o «create invoice».

### `get_page` (~58 tokens)

Leer una página

El texto completo (Markdown) de una página de la documentación, por su ruta, por ejemplo /docs/api/facturas o /docs/api/referencia/facturas/create-invoice.

Input parameters:

- `path` (string, required): La ruta de la página.

### `list_operations` (~68 tokens)

Operaciones de la API

Las operaciones de la API (operationId, método, ruta y qué hace), por sección. Úsela para encontrar la ruta correcta antes de describe_operation.

Input parameters:

- `tag` (string): Solo las de esta sección, por ejemplo «Facturas», «Webhooks» o en inglés «Invoices».

### `describe_operation` (~165 tokens)

Describir una operación

Todo sobre una operación: parámetros, cada campo del cuerpo (tipo, si es obligatorio, límites), ejemplos, el código con el SDK del lenguaje que elija y qué objeto contesta (sus campos con describe_object, o aquí con full).

Input parameters:

- `full` (boolean): true: también la tabla de cada campo de la respuesta (larga). Por omisión solo su nombre y un ejemplo.
- `language` (string): El SDK del ejemplo de código. Por omisión ts.
- `operation` (string, required): El operationId (createInvoice), el método del SDK (invoices.create), el método y la ruta («POST /v1/invoices», «GET /v1/invoices/inv_123») o en palabras («create invoice», «cancelar factura»).

### `describe_object` (~58 tokens)

Describir un objeto

Los campos de un objeto que contesta la API (Invoice, Customer, Event, Error…), con su tipo y significado, y un ejemplo. Sin nombre, la lista de objetos.

Input parameters:

- `name` (string): El objeto, por ejemplo Invoice.

### `explain_error` (~48 tokens)

Explicar un error

Qué significa un código de error de la API (el error.code de la respuesta, por ejemplo issuer_required) y cómo resolverlo.

Input parameters:

- `code` (string, required): El error.code de la respuesta.

### `call_api` (~191 tokens)

Probar en modo de pruebas

Hace una solicitud real a la API en modo de pruebas con la llave fk_test_ de la persona (nunca una fk_live_) y devuelve el código, el Request-Id y el JSON de la respuesta. Para probar un cuerpo antes de escribir el código. Timbra con el emisor de pruebas del SAT, sin costo.

Input parameters:

- `api_key` (string, required): La llave de pruebas (fk_test_…) de la persona, de Desarrolladores › Llaves. Pídasela; no la invente.
- `body` (object): El cuerpo JSON, para POST.
- `idempotency_key` (string): Idempotency-Key del POST (por omisión una nueva): repetirla con lo mismo contesta lo de la primera vez.
- `method` (string, required)
- `path` (string, required): La ruta con su consulta, por ejemplo /v1/invoices?limit=3.

### `list_pages` (~29 tokens)

Todas las páginas

Todas las páginas de la documentación: guías y referencia, con su ruta y de qué tratan.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-fiscalisto-docs/docs-api-mcp#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 69
- 2026-10-27: 69

## Common questions

### What is the Fiscalisto API docs MCP server?

Fiscalisto API docs is an MCP server listed in the public MCP registry as com.fiscalisto/docs. Docs for Fiscalisto's Mexican e-invoicing API (CFDI 4.0): search, operations, SDK code, errors. This page covers its hosted endpoint (https://fiscalisto.com/docs/api/mcp).

### Is the Fiscalisto API docs MCP server safe to use?

Fiscalisto API docs scores 73 out of 100 on VerifyMCP. 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 Fiscalisto API docs MCP server expose?

Fiscalisto API docs exposes 9 tools: get_started, search_docs, get_page, list_operations, describe_operation, and 4 more. Their descriptions and schemas cost roughly 803 tokens of context every time the server is loaded.

### Does the Fiscalisto API docs MCP server require authentication?

No. We connected to Fiscalisto API docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Fiscalisto API docs MCP server still maintained?

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

### What did VerifyMCP test on the Fiscalisto API docs MCP server?

VerifyMCP ran 12 checks on Fiscalisto API docs, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Fiscalisto API docs: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://fiscalisto.com/docs/api/mcp
- Website: https://fiscalisto.com/docs/api/agentes
- Changelog RSS feed: https://verifymcp.io/servers/com-fiscalisto-docs/docs-api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-fiscalisto-docs/docs-api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-fiscalisto-docs/docs-api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-fiscalisto-docs/docs-api-mcp