Remote MCP · Endpoint

Palmera property catalog MCP server

No. Palmera property catalog answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://api.palmera.realestate/api/v1/ai/mcp

The last check completed an MCP handshake.

Registry name
realestate.palmera/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
259 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Off-plan and ready property in the UAE, Oman, Georgia, Cyprus, Bali, Thailand and London.
Listing
From the official MCP registry (active).
Recent checks of Palmera property catalog
CheckedResultHandshake
33 minutes agoHandshake completed259 ms
3 days agoHandshake completed256 ms
13 days agoHandshake completed304 ms
13 days agoHandshake completed277 ms
15 days agoHandshake completed255 ms
16 days agoHandshake completed263 ms
17 days agoHandshake completed292 ms
18 days agoHandshake completed270 ms
18 days agoHandshake completed262 ms
20 days agoHandshake completed254 ms
22 days agoHandshake completed260 ms
25 days agoHandshake completed252 ms
27 days agoHandshake completed7.92 s

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