Ecuafact MCP server

• Registry namecom.ecuafact.docsapi/documentacionverified in the MCP registry

The registry name sits under ecuafact.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-20
• Tools6
• Server calls itselfecuafact-docs
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 460 ms.

• Its tools do none of the product's use cases we checked: sign electronic documents with a digital certificate; review received documents and reports in one account.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it0 of 2 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer568 ms
• Space in an agent's context≈ 638 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsB · 86 of 100
• Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

• Parameters without a type: in 5 of 6

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• ejemplo_comprobante

  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.

• explicar_error

  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.

• leer_guia

  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.

• buscar_documentacion

  Busca en la documentacion y devuelve las guias relevantes con un fragmento y su URL. Despues, lee la guia con leer_guia.

• consultar_referencia

  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.

• listar_guias

  Lista las guias de la documentacion agrupadas por tema, con su slug, una descripcion corta y su URL.