Fiscalisto API docs
REMOTE · FISCALISTO.COM
Docs for Fiscalisto's Mexican e-invoicing API (CFDI 4.0): search, operations, SDK code, errors.
Available components
Last scanned (4 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 990 tokens (~110/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 28 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 69
First indexed and scored.
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 5 Nov 2026 · Probed https://fiscalisto.com/docs/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fiscalisto.com | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 22306df8ab12c0f70e4e5383e8242787 |
| SANs: fiscalisto.com, api.fiscalisto.com, *.api.fiscalisto.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fiscalisto.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fiscalisto.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
| permissions-policy | camera=(self), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fiscalisto.com/docs/api/mcp | Verified | 200 | |
| http (plaintext) | http://fiscalisto.com/docs/api/mcp | Inconclusive | 405 |
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 →
call_api Probar en modo de pruebas ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | 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 | yes | – |
| path | string | yes | La ruta con su consulta, por ejemplo /v1/invoices?limit=3. |
No output schema declared.
No examples provided.
describe_object Describir un objeto ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | El objeto, por ejemplo Invoice. |
No output schema declared.
No examples provided.
describe_operation Describir una operación ~165
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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»). |
No output schema declared.
No examples provided.
explain_error Explicar un error ~48
Qué significa un código de error de la API (el error.code de la respuesta, por ejemplo issuer_required) y cómo resolverlo.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | El error.code de la respuesta. |
No output schema declared.
No examples provided.
get_page Leer una página ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | La ruta de la página. |
No output schema declared.
No examples provided.
get_started Cómo integrar Fiscalisto ~92
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_operations Operaciones de la API ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tag | string | – | Solo las de esta sección, por ejemplo «Facturas», «Webhooks» o en inglés «Invoices». |
No output schema declared.
No examples provided.
list_pages Todas las páginas ~29
Todas las páginas de la documentación: guías y referencia, con su ruta y de qué tratan.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_docs Buscar en la documentación ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Palabras a buscar, en español o inglés, por ejemplo «cancelar factura motivo 02» o «create invoice». |
No output schema declared.
No examples provided.
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.
remote · fiscalisto.com
claude mcp add --transport http com-fiscalisto-docs 'https://fiscalisto.com/docs/api/mcp'
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.