# CasaCaddy Maintenance (remote · api.casacaddy.com)

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

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `api.casacaddy.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-soxoa-casacaddy-maintenance/api.md), [page](https://verifymcp.io/servers/com-soxoa-casacaddy-maintenance/api)

## Channel facts

- Endpoint: `https://api.casacaddy.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 348 tokens (~116/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-soxoa-casacaddy-maintenance 'https://api.casacaddy.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-soxoa-casacaddy-maintenance": {
      "url": "https://api.casacaddy.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-soxoa-casacaddy-maintenance": {
      "type": "http",
      "url": "https://api.casacaddy.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-soxoa-casacaddy-maintenance]
url = "https://api.casacaddy.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-soxoa-casacaddy-maintenance": {
      "type": "remote",
      "url": "https://api.casacaddy.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-soxoa-casacaddy-maintenance --url 'https://api.casacaddy.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-soxoa-casacaddy-maintenance:
    url: "https://api.casacaddy.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-soxoa-casacaddy-maintenance": {
      "Transport": "http",
      "Url": "https://api.casacaddy.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-soxoa-casacaddy-maintenance -t streamable-http -u 'https://api.casacaddy.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-02 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-01 (score 71)

First indexed and scored.

## MCP tools (3)

### `get_connected_installation` (~45 tokens)

Connected CasaCaddy installation

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.

### `get_maintenance_guide` (~152 tokens)

Get a CasaCaddy maintenance guide

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.

Input parameters:

- `item` (object, required)
- `question` (string)
- `request_key` (string, required)
- `use_existing_allowance` (boolean, required)

### `get_saved_guide_request` (~78 tokens)

Recover a guide request

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.

Input parameters:

- `request_key` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-soxoa-casacaddy-maintenance/api#diagnostics

## Score history

- 2026-10-03: 72
- 2026-10-02: 72
- 2026-10-01: 71

## Common questions

### 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.

## Links

- Remote endpoint: https://api.casacaddy.com/mcp
- Website: https://api.casacaddy.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/com-soxoa-casacaddy-maintenance/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-soxoa-casacaddy-maintenance/api.json
- HTML version of this page: https://verifymcp.io/servers/com-soxoa-casacaddy-maintenance/api