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
437 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search public property listings in Portugal, compare homes and read INE housing statistics.
Website
https://casanest.eu/ia
Listing
From the official MCP registry (active).
Recent checks of CasaNest
CheckedResultHandshake
1 hour agoHandshake completed437 ms
8 days agoHandshake completed521 ms
9 days agoHandshake completed447 ms
11 days agoHandshake completed459 ms
12 days agoHandshake completed450 ms
12 days agoHandshake completed329 ms
14 days agoHandshake completed396 ms
14 days agoHandshake completed453 ms
16 days agoHandshake completed584 ms
19 days agoHandshake completed559 ms
21 days agoHandshake completed625 ms
24 days agoHandshake completed371 ms
26 days agoHandshake completed168 ms
28 days agoHandshake completed385 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.