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

Burofácil

https://burofacil.es

Registry code: 32fd652eaca847b9

api record

Burofácil: redacta, comprueba y envía burofaxes con validez legal en España, válidos como intento de negociación MASC (LO 1/2025). Esto no es asesoramiento jurídico. Tú envías en tu nombre; nosotros te damos el texto y el canal. Si tu caso es complejo (familia, penal, laboral con plazo, cuantías altas), te lo diremos y te recomendaremos hablar con un abogado. El envío se paga en la web; ninguna herramienta cobra ni envía por sí sola.

endpoint
https://burofacil.es/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 Burofácil live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is Burofácil free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does Burofácil have?
5 tools: redactar_burofax, enviar_burofax, validar_masc, listar_casos, estado_envio.
Is Burofácil 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
98.5%

90 days 99.2%· all time 99.2%

latency
1,246ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 251 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • unknown → live
_ what it is for
used for
  • draft a spanish burofax
  • validate a burofax against masc rules
  • prepare a burofax for sending
  • check status of a burofax
takes → gives
text → text, documents
tools
4 reads1 changes data
_ 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 5 tools
1 open1 auth-required 3 never probed 2 of 5 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.

  • listar_casos reads open 2h ago

    Lista los tipos de burofax que se pueden redactar (slug, nombre, cuándo usarlo y qué datos pide cada uno).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • estado_envio reads auth-required 2h ago

    Estado de un expediente por su token: borrador, pagado, enviado, entregado o intento documentado; fechas del día 15 y 30; enlaces a la evidencia y al dossier.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "token"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "Token del expediente (el de los enlaces /e/ o /borrador/)"
        }
      }
    }
    arguments 13 lines
  • redactar_burofax reads unknown never probed

    Redacta el burofax de un caso (ver listar_casos) a partir de los datos. Devuelve el texto, el semáforo de requisitos y un token de borrador que enviar_burofax puede usar. No envía ni cobra.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "caso",
        "datos",
        "email"
      ],
      "properties": {
        "caso": {
          "enum": [
            "burofax-masc",
            "burofax-fin-contrato-alquiler",
            "burofax-impago-alquiler",
            "reclamar-fianza-alquiler",
            "burofax-reclamacion-deuda",
            "burofax-impago-comunidad",
            "carta-baja-permanencia",
            "burofax-reclamacion-aseguradora",
            "burofax-garantia-desistimiento",
            "burofax-reclamacion-cantidad-laboral",
            "burofax-vecino-ruidos-humedades",
            "burofax-reclamar-obra-reforma-taller"
          ],
          "type": "string",
          "description": "slug del caso, de listar_casos"
        },
        "datos": {
          "type": "object",
          "description": "Respuestas por clave (ver datos de listar_casos). Fechas AAAA-MM-DD, importes solo número.",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {
            "type": "string"
          }
        },
        "email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "description": "Email del remitente: recibe el enlace al borrador y la evidencia"
        }
      }
    }
    arguments 45 lines
  • enviar_burofax changes data unknown never probed

    Deja un burofax listo para enviarse en papel con acuse de recibo (destinatario con dirección en España) y devuelve el enlace donde el remitente revisa, completa, firma y paga (29 € texto propio, 49 € redactado, 59 € pack MASC). Acepta un borrador_token de redactar_burofax o un texto propio. Lo que no sepas, escríbelo como [DATO PENDIENTE: qué falta] y la web lo pide en un formulario. Si lo va a firmar y pagar otra persona, pasa compartir: true y dale el enlace al usuario para que se lo envíe. No cobra ni envía sin que alguien pague en la web.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "email"
      ],
      "properties": {
        "canal": {
          "enum": [
            "electronico",
            "postal"
          ],
          "type": "string",
          "description": "Ignorado: todo envío va en papel (postal certificado) a destinatario_direccion; si hay destinatario_email, además por email certificado"
        },
        "email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "description": "Email del remitente"
        },
        "texto": {
          "type": "string",
          "maxLength": 20000,
          "minLength": 80,
          "description": "Texto propio, si no hay borrador_token. Los datos que falten, como [DATO PENDIENTE: nombre del presidente]"
        },
        "compartir": {
          "type": "boolean",
          "description": "true si lo va a firmar y pagar otra persona (el presidente de una comunidad, un familiar, un cliente): entonces `email` es el de quien lo prepara, que recibe copia de todos los avisos, y el enlace devuelto se comparte con quien lo envía"
        },
        "borrador_token": {
          "type": "string",
          "description": "Token devuelto por redactar_burofax"
        },
        "remitente_nombre": {
          "type": "string",
          "description": "Nombre de quien envía, si se sabe; si no, lo pone quien abra el enlace"
        },
        "destinatario_email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "description": "Email del destinatario, para envío electrónico"
        },
        "destinatario_nombre": {
          "type": "string",
          "description": "Nombre o empresa del destinatario"
        },
        "destinatario_direccion": {
          "type": "string",
          "description": "Dirección postal del destinatario"
        }
      }
    }
    arguments 55 lines
  • validar_masc reads unknown 2h ago

    Evalúa un burofax ya escrito contra los cinco requisitos del intento de negociación de la Ley 1/2025 (quién, a quién, qué, cuánto, propuesta con plazo). Devuelve un semáforo por requisito con qué falta. Gratis; no guarda nada.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "texto"
      ],
      "properties": {
        "texto": {
          "type": "string",
          "maxLength": 20000,
          "minLength": 80,
          "description": "Texto íntegro del burofax"
        }
      }
    }
    arguments 15 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 32fd652eaca847b9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/32fd652eaca847b9/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/32fd652eaca847b9/badge.svg)](https://brick.blue/agent/32fd652eaca847b9?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
90%

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.