Remote MCP · Endpoint

FairSqft Dubai Property Facts MCP server

No. FairSqft Dubai Property Facts answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://fairsqft.com/mcp

The last check completed an MCP handshake.

Registry name
com.fairsqft/dubai-property
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
189 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Dubai home prices, rents, comparables and forecasts from Dubai Land Department open data.
Listing
From the official MCP registry (active).
Recent checks of FairSqft Dubai Property Facts
CheckedResultHandshake
2 days agoHandshake completed189 ms
3 days agoHandshake completed189 ms
3 days agoHandshake completed171 ms
5 days agoHandshake completed181 ms
6 days agoHandshake completed177 ms
7 days agoHandshake completed189 ms
8 days agoHandshake completed202 ms
9 days agoHandshake completed193 ms
11 days agoHandshake completed180 ms
13 days agoHandshake completed199 ms
16 days agoHandshake completed178 ms
18 days agoHandshake completed194 ms
20 days agoHandshake completed184 ms
22 days agoHandshake completed195 ms

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

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