Remote MCP · Endpoint

Cubi Estate MCP server

No. Cubi Estate answered an MCP handshake 26 minutes ago.

UpLast checked 26 minutes ago

Server URL

https://mcp.cubi.estate/mcp

The last check completed an MCP handshake.

Registry name
estate.cubi/cubi-properties
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
247 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search 2.5M+ homes to buy or rent in 17 European countries. Compare prices, history, similar homes.
Listing
From the official MCP registry (active).
Recent checks of Cubi Estate
CheckedResultHandshake
26 minutes agoHandshake completed247 ms
10 days agoHandshake completed279 ms
11 days agoHandshake completed246 ms
12 days agoHandshake completed244 ms
13 days agoHandshake completed247 ms
14 days agoHandshake completed254 ms
15 days agoHandshake completed258 ms
16 days agoHandshake completed246 ms
17 days agoHandshake completed271 ms
19 days agoHandshake completed390 ms
22 days agoHandshake completed257 ms
24 days agoHandshake completed245 ms
26 days agoHandshake completed252 ms
29 days agoHandshake completed229 ms

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

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