Skip to content
MCP server

CasaCaddy Maintenance

By soxoaAll Soxoa servers

Read guide requirements, prepare confirmed maintenance guides and check your device-owned jobs.

First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

1
Directories
Collected by InvokeRank
3
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data

Tools

ToolDescriptionBehaviour
get_connected_installationIdentify the linked CasaCaddy Pro installation and its current maintenance-guide allowance. No device identifier, billing data, on-device home library, appliance list or task history is exposed.Read-only
get_maintenance_guideUse the linked Pro installation to request a maintenance guide for the appliance details and question the user supplied. Ask for confirmation before using existing Pro allowance; a fresh guide uses that allowance and the existing external model pipeline. Existing exact-input cached guides are unmetered. Supply a fresh UUID request_key and reuse it for retries: identical-key results are persisted, so a retry never starts a second provider request. Preserve safetyWarnings, step cautions, whenToCallPro and call_a_pro difficulty. This does not read on-device appliances or schedule tasks.Changes data
get_saved_guide_requestRecover one maintenance-guide request made through MCP by the linked installation, using its exact request_key. Only that installation’s request records are returned, for up to 30 days. Does not start generation, consume allowance or read the on-device library. Keep all safety warnings and professional-help boundaries intact.Read-only

Directory listings

DirectoryListingTierFirst seen
Official MCP RegistryCasaCaddy Maintenance-2 Oct 2026