Remote MCP · Endpoint

Casatoo MCP server

No. Casatoo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.casatoo.pt/mcp

The last check completed an MCP handshake.

Registry name
pt.casatoo/casatoo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
629 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search and compare current homes across Portuguese real-estate portals with Casatoo's hosted MCP.
Listing
From the official MCP registry (active).
Recent checks of Casatoo
CheckedResultHandshake
1 hour agoHandshake completed629 ms
2 days agoHandshake completed199 ms
4 days agoHandshake completed231 ms
5 days agoHandshake completed574 ms
7 days agoHandshake completed591 ms
8 days agoHandshake completed574 ms
9 days agoHandshake completed443 ms
12 days agoHandshake completed536 ms
13 days agoHandshake completed585 ms
15 days agoHandshake completed561 ms
17 days agoHandshake completed539 ms
18 days agoHandshake completed549 ms
19 days agoHandshake completed201 ms
20 days agoHandshake completed540 ms
21 days agoHandshake completed536 ms
21 days agoHandshake completed202 ms
23 days agoHandshake completed186 ms

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

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