Remote MCP · Endpoint

Boe Legislacion MCP server

No. Boe Legislacion answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://gateway.pipeworx.io/boe-legislacion/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/boe-legislacion
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
848 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Spain consolidated legislation — Agencia Estatal Boletín Oficial del Estado (BOE), open-data API.
Listing
From the official MCP registry (active).
Recent checks of Boe Legislacion
CheckedResultHandshake
34 minutes agoHandshake completed848 ms
8 days agoHandshake completed359 ms
9 days agoHandshake completed84 ms
11 days agoHandshake completed983 ms
12 days agoHandshake completed1.96 s
13 days agoHandshake completed920 ms
14 days agoHandshake completed884 ms
14 days agoHandshake completed104 ms
16 days agoHandshake completed1.07 s
19 days agoHandshake completed1.33 s
21 days agoHandshake completed1.63 s
24 days agoHandshake completed109 ms
26 days agoHandshake completed272 ms
28 days agoHandshake completed1.09 s

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

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 Boe Legislacion and makes no claim about it beyond what these checks measured.