Remote MCP · Endpoint

Piso Radar MCP server

No. Piso Radar answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://pisoradar.es/mcp

The last check completed an MCP handshake.

Registry name
es.pisoradar/piso-radar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
209 ms
Tools exposed
6 tools
Uptime, last 30 days
4 checks from 4 checks
Described by its publisher as
Subastas de viviendas del BOE y pisos de banco en España: búsqueda, fichas, cierres y mercado.
Listing
From the official MCP registry (active).
Recent checks of Piso Radar
CheckedResultHandshake
43 minutes agoHandshake completed209 ms
10 days agoHandshake completed182 ms
10 days agoHandshake completed1.01 s
11 days agoHandshake completed1.01 s

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

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