Burofácil
REMOTE · BUROFACIL.ES
Draft, check and send a Spanish burofax (postal, proof of delivery), also from abroad.
Available components
Last scanned (3 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 833 tokens (~166/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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://burofacil.es/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=burofacil.es | CN=YE1,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 682d6093d88052d25c88f7bf04b11c810a1 |
| SANs: burofacil.es, www.burofacil.es | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of burofacil.es. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| es. | present | 4901, 54404 | 8, 8 | Verified |
| burofacil.es. | 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=15724800; includeSubdomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://burofacil.es/api/mcp | Verified | 200 | |
| http (plaintext) | http://burofacil.es/api/mcp | HTTPS enforced | 301 | https://burofacil.es:443/api/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 →
enviar_burofax Preparar el envío certificado ~400
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.
| Name | Type | Req | Description |
|---|---|---|---|
| borrador_token | string | – | Token devuelto por redactar_burofax |
| canal | string | – | Ignorado: todo envío va en papel (postal certificado) a destinatario_direccion; si hay destinatario_email, además por email certificado |
| compartir | boolean | – | 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 de… |
| destinatario_direccion | string | – | Dirección postal del destinatario |
| destinatario_email | string | – | Email del destinatario, para envío electrónico |
| destinatario_nombre | string | – | Nombre o empresa del destinatario |
| string | yes | Email del remitente | |
| remitente_nombre | string | – | Nombre de quien envía, si se sabe; si no, lo pone quien abra el enlace |
| texto | string | – | Texto propio, si no hay borrador_token. Los datos que falten, como [DATO PENDIENTE: nombre del presidente] |
No output schema declared.
No examples provided.
estado_envio Estado de un envío ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Token del expediente (el de los enlaces /e/ o /borrador/) |
No output schema declared.
No examples provided.
listar_casos Casos disponibles ~36
Lista los tipos de burofax que se pueden redactar (slug, nombre, cuándo usarlo y qué datos pide cada uno).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
redactar_burofax Redactar un burofax con los datos del caso ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caso | string | yes | slug del caso, de listar_casos |
| datos | object | yes | Respuestas por clave (ver datos de listar_casos). Fechas AAAA-MM-DD, importes solo número. |
| string | yes | Email del remitente: recibe el enlace al borrador y la evidencia |
No output schema declared.
No examples provided.
validar_masc Comprobar los requisitos MASC de un texto ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| texto | string | yes | Texto íntegro del burofax |
No output schema declared.
No examples provided.
How do I install the Burofácil MCP server?
Burofácil is a hosted endpoint at https://burofacil.es/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 · burofacil.es
claude mcp add --transport http pedropaf-burofacil 'https://burofacil.es/api/mcp'
What is the Burofácil MCP server?
Burofácil is an MCP server listed in the public MCP registry as io.github.pedropaf/burofacil. Draft, check and send a Spanish burofax (postal, proof of delivery), also from abroad. This page covers its hosted endpoint (https://burofacil.es/api/mcp).
Is the Burofácil MCP server safe to use?
Burofácil scores 80 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 Burofácil MCP server expose?
Burofácil exposes 5 tools: listar_casos, validar_masc, redactar_burofax, enviar_burofax, estado_envio. Their descriptions and schemas cost roughly 718 tokens of context every time the server is loaded.
Does the Burofácil MCP server require authentication?
No. We connected to Burofácil without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Burofácil MCP server still maintained?
Burofácil 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.