Remote MCP · Endpoint

CasaNest MCP server

No. CasaNest answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://casanest.eu/mcp

The last check completed an MCP handshake.

Registry name
eu.casanest/catalogue
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
385 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search public property listings in Portugal, compare homes and read INE housing statistics.
Listing
From the official MCP registry (active).
Recent checks of CasaNest
CheckedResultHandshake
1 hour agoHandshake completed385 ms
2 days agoHandshake completed368 ms
4 days agoHandshake completed383 ms
6 days agoHandshake completed360 ms
7 days agoHandshake completed390 ms
9 days agoHandshake completed367 ms
10 days agoHandshake completed394 ms
11 days agoHandshake completed361 ms
14 days agoHandshake completed362 ms
15 days agoHandshake completed418 ms
17 days agoHandshake completed518 ms
18 days agoHandshake completed442 ms
19 days agoHandshake completed389 ms
21 days agoHandshake completed401 ms
21 days agoHandshake completed456 ms
22 days agoHandshake completed420 ms
23 days agoHandshake completed487 ms

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

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