_ registry / mcp streamable-http · checked 1h ago

fiscalisto-docs

https://fiscalisto.com

Registry code: 2ef6c783046ad73c

api record

Documentación de la API de facturación electrónica mexicana (CFDI 4.0) de Fiscalisto. Para integrarla en una app, llame primero a get_started: es la guía completa en una página. Después busque con search_docs (español o inglés) y lea con get_page; describe_operation da cada ruta con sus campos y el código del SDK del lenguaje que pida, describe_object los objetos y explain_error los códigos de error. Con la llave de pruebas de la persona (pídasela; no la invente), call_api prueba una solicitud de verdad en modo de pruebas antes de escribir el código. Base: https://api.fiscalisto.com/v1;…

endpoint
https://fiscalisto.com/docs/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is fiscalisto-docs live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is fiscalisto-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does fiscalisto-docs have?
9 tools: get_started, search_docs, get_page, describe_operation, explain_error, call_api, list_operations, list_pages, ….
Is fiscalisto-docs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
264ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
3 open 6 never probed 3 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_operations open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "tag": {
          "type": "string",
          "description": "Solo las de esta sección, por ejemplo «Facturas», «Webhooks» o en inglés «Invoices»."
        }
      }
    }
    arguments 9 lines
  • list_pages open 1h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • describe_object open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "name": {
          "type": "string",
          "description": "El objeto, por ejemplo Invoice."
        }
      }
    }
    arguments 9 lines
  • get_started unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • search_docs unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Palabras a buscar, en español o inglés, por ejemplo «cancelar factura motivo 02» o «create invoice»."
        }
      }
    }
    arguments 12 lines
  • get_page unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "path"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "La ruta de la página."
        }
      }
    }
    arguments 12 lines
  • describe_operation unknown never probed

    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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "operation"
      ],
      "properties": {
        "full": {
          "type": "boolean",
          "description": "true: también la tabla de cada campo de la respuesta (larga). Por omisión solo su nombre y un ejemplo."
        },
        "language": {
          "enum": [
            "ts",
            "python",
            "php",
            "csharp",
            "go",
            "java",
            "all"
          ],
          "type": "string",
          "description": "El SDK del ejemplo de código. Por omisión ts."
        },
        "operation": {
          "type": "string",
          "description": "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»)."
        }
      }
    }
    arguments 29 lines
  • explain_error unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "El error.code de la respuesta."
        }
      }
    }
    arguments 12 lines
  • call_api unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "method",
        "path",
        "api_key"
      ],
      "properties": {
        "body": {
          "type": "object",
          "description": "El cuerpo JSON, para POST."
        },
        "path": {
          "type": "string",
          "description": "La ruta con su consulta, por ejemplo /v1/invoices?limit=3."
        },
        "method": {
          "enum": [
            "GET",
            "POST",
            "DELETE"
          ],
          "type": "string"
        },
        "api_key": {
          "type": "string",
          "description": "La llave de pruebas (fk_test_…) de la persona, de Desarrolladores › Llaves. Pídasela; no la invente."
        },
        "idempotency_key": {
          "type": "string",
          "description": "Idempotency-Key del POST (por omisión una nueva): repetirla con lo mismo contesta lo de la primera vez."
        }
      }
    }
    arguments 34 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2ef6c783046ad73c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2ef6c783046ad73c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2ef6c783046ad73c/badge.svg)](https://brick.blue/agent/2ef6c783046ad73c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.