Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Homey-Wan-Kenobi MCP

OCI · DOCKER.IO/RINGOSYSTEMS/HOMEY-WAN-KENOBI:2.2.0

MCP server for Homey Pro: 60 tools for devices, flows, energy, and Z-Wave/Zigbee diagnostics.

0 this week 57 Trust /100

Last scanned (19 hours ago)

Scores higher than 97% of OCI servers

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 126 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability88
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 3286 tokens (~54/item across 60 items; 60 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 60 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

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.

  • 23 Oct 26 0
    • Stability: 0.97 → pass security
  • 22 Oct 26 0
    • Stability: pass → 0.97 functional
  • 16 Oct 26 0
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +4
    • Provenance: unverified → fail ▼ security
    • Maintenance: unverified → pass ▲ functional
    • License: unverified → pass ▲ functional
    • Licence: MIT functional
  • 10 Oct 26 −4
    • Provenance: fail → unverified ▼ security
    • License: pass → unverified ▼ functional
    • Maintenance: pass → unverified ▼ functional
    • Licence: MIT functional
  • 4 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 4 Nov 2026 · Analysed oci/docker.io/ringosystems/homey-wan-kenobi:2.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 60 exposed · ~3,286 tokens

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 →

Tool Tokens
set_flow_enabled ~54

Enable or disable a flow automation. Disabled flows won't trigger. Use list_flows to find the flow ID.

NameTypeReqDescription
enabledbooleanyestrue to enable, false to disable
idstringyesFlow ID

No output schema declared.

No examples provided.

set_ledring ~58

Set the LED ring screensaver animation. Use get_ledring to see available options (e.g. 'spectrum', 'off').

NameTypeReqDescription
screensaverIdstringyesScreensaver ID (e.g. 'spectrum', 'off')

No output schema declared.

No examples provided.

set_mood ~51

Activate a mood (scene) in a zone. This sets all devices in the mood to their saved states.

NameTypeReqDescription
moodIdstringyesMood ID
zoneIdstringyesZone ID

No output schema declared.

No examples provided.

set_presence ~60

Set your own presence (home/away) or sleep state (awake/asleep). This affects presence-based automations.

NameTypeReqDescription
asleepboolean–true = asleep, false = awake
presentboolean–true = home, false = away

No output schema declared.

No examples provided.

set_system_name ~36

Set the Homey system name (visible in network discovery and the Homey app).

NameTypeReqDescription
namestringyesNew system name

No output schema declared.

No examples provided.

set_variable ~58

Set the value of a logic variable. The value type must match the variable type (boolean, number, or string).

NameTypeReqDescription
idstringyesVariable ID
valueboolean|number|stringyesNew value (must match variable type)

No output schema declared.

No examples provided.

trigger_flow ~48

Trigger (run) a flow immediately by its ID. Tries simple flow first, then advanced flow. Use list_flows to find the flow ID.

NameTypeReqDescription
idstringyesFlow ID

No output schema declared.

No examples provided.

uninstall_app ~35

Permanently uninstall a Homey app and remove all its devices. This cannot be undone.

NameTypeReqDescription
idstringyesApp ID

No output schema declared.

No examples provided.

update_advanced_flow ~100

Update an existing Advanced Flow. Pass only the fields to change (name, enabled, and/or the full cards map). Replacing cards replaces the entire flow graph, so fetch with get_advanced_flow first and send the complete cards object. Returns broken status.

NameTypeReqDescription
cardsobject–Full cards map (replaces existing)
enabledboolean––
idstringyesAdvanced Flow ID
namestring––

No output schema declared.

No examples provided.

update_flow ~57

Update a standard Flow. Pass the flow id and a 'flow' object with only the fields to change (name, trigger, conditions, actions, enabled).

NameTypeReqDescription
flowobjectyesFields to update
idstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Homey-Wan-Kenobi MCP server?

Homey-Wan-Kenobi MCP runs locally as a container image, launched with docker run --rm -i -e HOMEY_ADDRESS -e HOMEY_TOKEN docker.io/ringosystems/homey-wan-kenobi:2.2.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · docker.io/ringosystems/homey-wan-kenobi:2.2.0

# add to Claude Code
claude mcp add ringosystems-homey-wan-kenobi-mcp -- docker run --rm -i -e HOMEY_ADDRESS -e HOMEY_TOKEN docker.io/ringosystems/homey-wan-kenobi:2.2.0

This image reads HOMEY_ADDRESS and HOMEY_TOKEN. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the Homey-Wan-Kenobi MCP server?

Homey-Wan-Kenobi MCP is listed in the public MCP registry as io.github.Ringosystems/homey-wan-kenobi-mcp. MCP server for Homey Pro: 60 tools for devices, flows, energy, and Z-Wave/Zigbee diagnostics. This page covers its container image (docker.io/ringosystems/homey-wan-kenobi:2.2.0).

Is the Homey-Wan-Kenobi MCP server safe to use?

Homey-Wan-Kenobi MCP scores 57 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 Homey-Wan-Kenobi MCP server expose?

Homey-Wan-Kenobi MCP exposes 60 tools: list_devices, get_device, search_devices, set_device_capability, list_zones, and 55 more. Their descriptions and schemas cost roughly 3,286 tokens of context every time the server is loaded.

Is the Homey-Wan-Kenobi MCP server still maintained?

Homey-Wan-Kenobi MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Homey-Wan-Kenobi MCP server under?

Homey-Wan-Kenobi MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.