Remote MCP · Endpoint

Muscat Properties catalogue MCP server

No. Muscat Properties catalogue answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://muscat.properties/mcp

The last check completed an MCP handshake.

Registry name
properties.muscat/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
198 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
New-build and off-plan property in Oman: projects by area, developer, bedrooms and budget in OMR.
Listing
From the official MCP registry (active).
Recent checks of Muscat Properties catalogue
CheckedResultHandshake
1 hour agoHandshake completed198 ms
3 days agoHandshake completed191 ms
12 days agoHandshake completed478 ms
13 days agoHandshake completed142 ms
15 days agoHandshake completed247 ms
15 days agoHandshake completed149 ms
17 days agoHandshake completed255 ms
18 days agoHandshake completed201 ms
18 days agoHandshake completed131 ms
20 days agoHandshake completed412 ms
22 days agoHandshake completed181 ms
25 days agoHandshake completed189 ms
27 days agoHandshake completed157 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 Muscat Properties catalogue and makes no claim about it beyond what these checks measured.