Remote MCP · Endpoint

RealEVR Estates MCP server

No. RealEVR Estates answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://estates.realevr.com/mcp

The last check completed an MCP handshake.

Registry name
com.realevr.estates/estates
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
305 ms
Tools exposed
4 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Search real homes in Africa (rent, BnB, sale, bank sales) with 360° virtual tours.
Listing
From the official MCP registry (active).
Recent checks of RealEVR Estates
CheckedResultHandshake
7 hours agoHandshake completed305 ms
4 days agoFailed - the hostname does not resolve—
14 days agoHandshake completed293 ms
15 days agoHandshake completed370 ms
15 days agoHandshake completed329 ms
17 days agoHandshake completed317 ms
18 days agoHandshake completed293 ms
19 days agoHandshake completed480 ms
20 days agoHandshake completed311 ms
21 days agoHandshake completed294 ms
23 days agoHandshake completed841 ms
26 days agoHandshake completed296 ms
28 days agoHandshake completed304 ms

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

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