Remote MCP · Endpoint

RAK Real Estate projects MCP server

No. RAK Real Estate projects answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://www.rak.realestate/mcp

The last check completed an MCP handshake.

Registry name
realestate.rak/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.05 s
Tools exposed
6 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Off-plan projects in Ras Al Khaimah, UAE: search by area, developer, budget and handover year.
Listing
From the official MCP registry (active).
Recent checks of RAK Real Estate projects
CheckedResultHandshake
33 minutes agoHandshake completed1.05 s
3 days agoHandshake completed325 ms
13 days agoHandshake completed731 ms
13 days agoFailed - the request timed out—
15 days agoHandshake completed537 ms
16 days agoHandshake completed1.14 s
17 days agoHandshake completed1.53 s
18 days agoHandshake completed1.01 s
18 days agoHandshake completed1.06 s
20 days agoHandshake completed934 ms
22 days agoHandshake completed606 ms
25 days agoHandshake completed1.63 s
27 days agoHandshake completed1.58 s

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

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