← Index

io.github.claymore666/ccu-mcp

io.github.claymore666/ccu-mcpv1.9.1Other

MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API

In-path gate · all MCP tools

Using io.github.claymore666/ccu-mcp in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-08-24 23:02 UTC
screened 2026-07-25tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidenceNo malicious instructions foundvia static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-08-04).

Contracts can change after screening, with no version bump. The gate pins io.github.claymore666/ccu-mcp’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-claymore666-ccu-mcp)](https://mcpindex.ai/server/io-github-claymore666-ccu-mcp)
HTML
<a href="https://mcpindex.ai/server/io-github-claymore666-ccu-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-claymore666-ccu-mcp" alt="mcpindex verdict" height="20" /></a>
Environment variables
CCU_HOST
required

Hostname or IP of your HomeMatic CCU (debmatic, CCU3, or OpenCCU/RaspberryMatic)

CCU_PASSWORD
requiredsecret

CCU admin password (same as the WebUI login)

CCU_USER

CCU username

CCU_HTTPS

Connect to the CCU via HTTPS (self-signed certificates supported)

CCU_PORT

CCU API port (80 for HTTP, 443 for HTTPS)

CACHE_DIR

Directory for the device type cache and session persistence

MCP_ALLOWED_ORIGINS

Comma-separated allowlist of browser origins. Unset = no cross-origin browser access (default-deny). An allowlisted origin is reflected exactly in Access-Control-Allow-Origin (never '*'); the list also drives DNS-rebinding origin checks

MCP_ALLOWED_HOSTS

Extra Host header values accepted by DNS-rebinding protection (comma-separated host:port); add your hostname when behind a proxy or container DNS name

CCU_PROFILES

Comma-separated names of multiple CCU targets (e.g. 'prod,dev'). Each profile takes the flat CCU_* settings prefixed CCU_<NAME>_ (CCU_PROD_HOST, ...), plus policy flags CCU_<NAME>_PROTECTED (writes need confirm:true) and CCU_<NAME>_READONLY. Unset = single default profile from the flat CCU_* vars

CCU_DEFAULT_PROFILE

Which profile from CCU_PROFILES is active at startup (default: the first listed)

CCU_TLS_VERIFY

Verify the CCU's TLS certificate against the system trust store. Only meaningful with CCU_HTTPS=true. Default false, because a CCU ships a self-signed certificate — prefer CCU_TLS_FINGERPRINT or CCU_CA_CERT to verify one of those

CCU_TLS_FINGERPRINT

Pin the CCU's self-signed leaf certificate by its SHA-256 fingerprint (hex, colons optional). The strongest option for an appliance: the connection is rejected unless the presented certificate matches. Takes precedence over CCU_CA_CERT

CCU_CA_CERT

Path to a PEM file holding the CCU's CA or self-signed certificate. The connection is then validated against it with standard chain verification

CCU_TIMEOUT

Timeout for a CCU JSON-RPC call, in MILLISECONDS

CCU_SCRIPT_TIMEOUT

Timeout for HomeMatic Script execution (ReGa), in MILLISECONDS — scripts are slower than plain API calls

CACHE_TTL

Lifetime of the on-disk device-type schema cache, in SECONDS

CCU_RATE_LIMIT_BURST

Token-bucket burst size for CCU requests — how many may be issued back to back

CCU_RATE_LIMIT_RATE

Sustained CCU request rate, in requests per second

RESOURCE_POLL_INTERVAL

How often MCP resources are polled for change notifications, in SECONDS

LOG_LEVEL

error | warn | info | debug. Logs are structured JSON on stderr

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
10
installability
25
documentation
15
stability
10
Alternatives in Other