Remote MCP · Endpoint

CasaCaddy Maintenance MCP server

No. CasaCaddy Maintenance answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.casacaddy.com/mcp

The last check completed an MCP handshake.

Registry name
com.soxoa/casacaddy-maintenance
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.03 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read guide requirements, prepare confirmed maintenance guides and check your device-owned jobs.
Listing
From the official MCP registry (active).
Recent checks of CasaCaddy Maintenance
CheckedResultHandshake
2 hours agoHandshake completed1.03 s
2 days agoHandshake completed960 ms
4 days agoHandshake completed484 ms
7 days agoHandshake completed534 ms
8 days agoHandshake completed875 ms
11 days agoHandshake completed541 ms
13 days agoHandshake completed603 ms
14 days agoHandshake completed590 ms
16 days agoHandshake completed80 ms
17 days agoHandshake completed95 ms
18 days agoHandshake completed93 ms
20 days agoHandshake completed231 ms
22 days agoHandshake completed152 ms
24 days agoHandshake completed110 ms

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

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