Ecuafact API · Documentación
REMOTE · DOCSAPI.ECUAFACT.COM
Documentación de Ecuafact API: facturación electrónica del SRI de Ecuador. Sin credenciales.
Available components
Last scanned (4 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Code Search and Documentation
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 Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 649 tokens (~108/item across 6 items; 6 tools + 0 resources), lean.Pass
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 5 Nov 26 +1
- The server no longer declares the “logging” capability functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +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.
- 29 Oct 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.
- 27 Oct 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.
- 25 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.
- 23 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.
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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://docsapi.ecuafact.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.ecuafact.com | CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB | 27 Sept 2026 | 13 Apr 2027 | RSA 2048 | SHA256-RSA | c93e5bcef4890c59bd8923a82ad5fd4c |
| SANs: *.ecuafact.com, ecuafact.com | ||||||
| CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 22 Mar 2021 | 21 Mar 2036 | RSA 3072 | SHA384-RSA | 397a66cc2756362e0daa87ca6eabe3b1 |
| CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | d27fbbc1de359e5216ad6149586099c4 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of docsapi.ecuafact.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ecuafact.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 |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-mZ4yH5Py/nzSfyRgi3Qu0Q=='; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self' ws: wss:; frame-src 'self'; frame-ancestors 'self'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docsapi.ecuafact.com/mcp | Verified | 200 | |
| http (plaintext) | http://docsapi.ecuafact.com/mcp | HTTPS enforced | 308 | https://docsapi.ecuafact.com/mcp |
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 →
buscar_documentacion ~89
Busca en la documentacion y devuelve las guias relevantes con un fragmento y su URL. Despues, lee la guia con leer_guia.
| Name | Type | Req | Description |
|---|---|---|---|
| consulta | – | yes | Que buscar, por ejemplo 'nota de credito', 'firma de webhooks' o 'Idempotency-Key'. |
| maximo | integer | – | Maximo de resultados (1 a 20, por defecto 8). |
No output schema declared.
No examples provided.
consultar_referencia ~106
Consulta el contrato OpenAPI del API. Sin ruta, lista los endpoints. Con ruta (y metodo), devuelve los parametros, el cuerpo, las respuestas y los esquemas que usa.
| Name | Type | Req | Description |
|---|---|---|---|
| metodo | – | – | Metodo HTTP: GET, POST, PUT o DELETE (opcional; por defecto el unico o el primero). |
| ruta | – | – | Ruta del endpoint como aparece en el listado, por ejemplo '/v1/contribuyentes/{identificacion}/comprobantes' (opcional). |
No output schema declared.
No examples provided.
ejemplo_comprobante ~105
Devuelve un JSON de ejemplo valido para emitir un tipo de comprobante (01 factura, 03 liquidacion de compra, 04 nota de credito, 05 nota de debito, 06 guia de remision, 07 retencion), con el enlace a su guia.
| Name | Type | Req | Description |
|---|---|---|---|
| tipo | – | yes | Tipo de comprobante: 01, 03, 04, 05, 06 o 07, o su nombre (factura, nota de credito...). |
No output schema declared.
No examples provided.
explicar_error ~83
Explica un codigo de error del catalogo de la API (tres digitos, por ejemplo 302 o 401): estado HTTP, mensaje, cuando ocurre, que hacer y si se reintenta. El codigo es el campo 'codigo' del cuerpo de error, no el estado HTTP.
| Name | Type | Req | Description |
|---|---|---|---|
| codigo | – | yes | Codigo del catalogo, por ejemplo '302'. |
No output schema declared.
No examples provided.
leer_guia ~109
Devuelve una guia en Markdown. Con seccion, devuelve solo la seccion cuyo titulo coincide; las guias largas (por ejemplo las de SDK) conviene leerlas por seccion.
| Name | Type | Req | Description |
|---|---|---|---|
| seccion | – | – | Titulo o parte del titulo de una seccion (opcional), por ejemplo 'Firma' o 'Catalogo de codigos'. |
| slug | – | yes | Slug de la guia, por ejemplo 'emision-01' o 'webhooks'. Tambien acepta su URL. |
No output schema declared.
No examples provided.
listar_guias ~33
Lista las guias de la documentacion agrupadas por tema, con su slug, una descripcion corta y su URL.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Ecuafact API · Documentación MCP server?
Ecuafact API · Documentación is a hosted endpoint at https://docsapi.ecuafact.com/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 · docsapi.ecuafact.com
claude mcp add --transport http com-ecuafact-docsapi-documentacion 'https://docsapi.ecuafact.com/mcp'
What is the Ecuafact API · Documentación MCP server?
Ecuafact API · Documentación is an MCP server listed in the public MCP registry as com.ecuafact.docsapi/documentacion. Documentación de Ecuafact API: facturación electrónica del SRI de Ecuador. Sin credenciales. This page covers its hosted endpoint (https://docsapi.ecuafact.com/mcp).
Is the Ecuafact API · Documentación MCP server safe to use?
Ecuafact API · Documentación scores 81 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 Ecuafact API · Documentación MCP server expose?
Ecuafact API · Documentación exposes 6 tools: listar_guias, buscar_documentacion, leer_guia, explicar_error, ejemplo_comprobante, consultar_referencia. Their descriptions and schemas cost roughly 525 tokens of context every time the server is loaded.
Does the Ecuafact API · Documentación MCP server require authentication?
No. We connected to Ecuafact API · Documentación without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Ecuafact API · Documentación MCP server still maintained?
Ecuafact API · Documentación 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.