Remote MCP · Endpoint
au.com.casaintelligence/casa-property MCP server
No. au.com.casaintelligence/casa-property answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.casaintelligence.com.au/mcp/public/v1/messages
The last check completed an MCP handshake.
- Registry name
- au.com.casaintelligence/casa-property
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 1.09 s
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Indicative SEQ Australia property planning intelligence: zones, overlays, subdivision, DA stats.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 1.09 s |
| 1 day ago | Handshake completed | 882 ms |
| 2 days ago | Handshake completed | 1.05 s |
| 3 days ago | Handshake completed | 1.14 s |
| 4 days ago | Handshake completed | 1.00 s |
| 5 days ago | Handshake completed | 1.66 s |
| 7 days ago | Handshake completed | 1.03 s |
| 10 days ago | Handshake completed | 1.10 s |
| 12 days ago | Handshake completed | 1.10 s |
| 15 days ago | Handshake completed | 1.07 s |
| 17 days ago | Handshake completed | 911 ms |
| 19 days ago | Handshake completed | 914 ms |
| 21 days ago | Handshake completed | 963 ms |
| 23 days ago | Handshake completed | 929 ms |
| 25 days ago | Handshake completed | 922 ms |
| 26 days ago | Handshake completed | 964 ms |
| 28 days ago | Handshake completed | 914 ms |
| 29 days ago | Handshake completed | 1.03 s |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 au.com.casaintelligence/casa-property and makes no claim about it beyond what these checks measured.