Remote MCP · Endpoint

Dubai Diligence MCP server

No. Dubai Diligence answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://dubaidiligence.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.stevenworlow/dubai-diligence-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
180 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Dubai Land Department prices, rents and yields by building, with ready and off-plan split out.
Listing
From the official MCP registry (active).
Recent checks of Dubai Diligence
CheckedResultHandshake
1 hour agoHandshake completed180 ms
1 day agoHandshake completed228 ms
2 days agoHandshake completed264 ms
3 days agoHandshake completed165 ms
3 days agoHandshake completed157 ms
5 days agoHandshake completed190 ms
7 days agoHandshake completed235 ms
10 days agoHandshake completed158 ms
12 days agoHandshake completed150 ms
14 days agoHandshake completed222 ms
17 days agoHandshake completed194 ms
19 days agoHandshake completed220 ms
21 days agoHandshake completed156 ms
23 days agoHandshake completed146 ms
24 days agoHandshake completed189 ms

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

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