Remote MCP · Endpoint

Burofácil MCP server

No. Burofácil answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://burofacil.es/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.pedropaf/burofacil
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
370 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Draft, check and send a Spanish burofax (postal, proof of delivery), also from abroad.
Listing
From the official MCP registry (active).
Recent checks of Burofácil
CheckedResultHandshake
1 hour agoHandshake completed370 ms
2 days agoHandshake completed334 ms
4 days agoHandshake completed318 ms
6 days agoHandshake completed321 ms
8 days agoHandshake completed313 ms
10 days agoHandshake completed314 ms
12 days agoHandshake completed416 ms
14 days agoHandshake completed331 ms
15 days agoHandshake completed338 ms
16 days agoHandshake completed313 ms
17 days agoHandshake completed311 ms
20 days agoHandshake completed313 ms
22 days agoHandshake completed320 ms
23 days agoHandshake completed350 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Burofácil and makes no claim about it beyond what these checks measured.