CasaCaddy Maintenance
REMOTE · API.CASACADDY.COM · SCANNED OCT 3
Read guide requirements, prepare confirmed maintenance guides and check your device-owned jobs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 348 tokens (~116/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the CasaCaddy Maintenance MCP server?
CasaCaddy Maintenance is a hosted endpoint at https://api.casacaddy.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.casacaddy.com
claude mcp add --transport http com-soxoa-casacaddy-maintenance 'https://api.casacaddy.com/mcp'
{
"mcpServers": {
"com-soxoa-casacaddy-maintenance": {
"url": "https://api.casacaddy.com/mcp"
}
}
} {
"servers": {
"com-soxoa-casacaddy-maintenance": {
"type": "http",
"url": "https://api.casacaddy.com/mcp"
}
}
} [mcp_servers.com-soxoa-casacaddy-maintenance] url = "https://api.casacaddy.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-soxoa-casacaddy-maintenance": {
"type": "remote",
"url": "https://api.casacaddy.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-soxoa-casacaddy-maintenance --url 'https://api.casacaddy.com/mcp' --transport streamable-http
mcp_servers:
com-soxoa-casacaddy-maintenance:
url: "https://api.casacaddy.com/mcp" {
"McpServers": {
"com-soxoa-casacaddy-maintenance": {
"Transport": "http",
"Url": "https://api.casacaddy.com/mcp"
}
}
} assistant mcp add com-soxoa-casacaddy-maintenance -t streamable-http -u 'https://api.casacaddy.com/mcp'
{
"mcpServers": {
"com-soxoa-casacaddy-maintenance": {
"type": "http",
"url": "https://api.casacaddy.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 1 Oct 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Oct 2026 · Probed https://api.casacaddy.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.casacaddy.com | CN=YR1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | RSA 2048 | SHA256-RSA | 53764c37a63b30513685df49220c892e5c0 |
| SANs: api.casacaddy.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.casacaddy.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| casacaddy.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.casacaddy.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.casacaddy.com/mcp | HTTPS enforced | 308 | https://api.casacaddy.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_connected_installation Connected CasaCaddy installation ~45
Identify 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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_maintenance_guide Get a CasaCaddy maintenance guide ~152
Use 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.
| Name | Type | Req | Description |
|---|---|---|---|
| item | object | yes | – |
| question | string | – | – |
| request_key | string | yes | – |
| use_existing_allowance | boolean | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_saved_guide_request Recover a guide request ~78
Recover 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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the CasaCaddy Maintenance MCP server?
CasaCaddy Maintenance is an MCP server listed in the public MCP registry as com.soxoa/casacaddy-maintenance. Read guide requirements, prepare confirmed maintenance guides and check your device-owned jobs. This page covers its hosted endpoint (https://api.casacaddy.com/mcp).
Is the CasaCaddy Maintenance MCP server safe to use?
CasaCaddy Maintenance scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CasaCaddy Maintenance MCP server expose?
CasaCaddy Maintenance exposes 3 tools: get_connected_installation, get_maintenance_guide, get_saved_guide_request. Their descriptions and schemas cost roughly 275 tokens of context every time the server is loaded.
Does the CasaCaddy Maintenance MCP server require authentication?
No. We connected to CasaCaddy Maintenance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CasaCaddy Maintenance MCP server still maintained?
CasaCaddy Maintenance is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.