openhab-mcp-server@1.1.1
CAUTION· not startedPublisher claims: "Model Context Protocol server for openHAB home automation" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
OPENHAB_TOKENor--openhab-tokenConfiguration, not credentials: HEALTH_CHECK_PORT, OPENHAB_RETRY_ATTEMPTS, OPENHAB_RETRY_BACKOFF_FACTOR, OPENHAB_RETRY_MAX_DELAY, OPENHAB_TIMEOUT, OPENHAB_URL- Where it talks to
- openhab.org (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for OPENHAB_TOKEN and talks to openhab.org. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 78/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Auto-update or dynamic fetch configuration. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
openhab-mcp-server --openhab-url http://192.168.1.100:8080Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.self.log(f"Error sending command to {item_name}: {e}")Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.result = subprocess.run([Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."; rm -rf /", # Command injectionFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.r'(/etc/passwd)',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."; rm -rf /", # Command injectionFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."; rm -rf /",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(cmd, check=True, capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(cmd, check=True, capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."; rm -rf /",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.auto_update: Optional[bool] = Field(None, description="Whether the link should auto-update the item")Fix: Pin versions and sources; vendor anything fetched at install time.openhab-mcp-server --openhab-url http://192.168.1.100:8080Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls."../../../etc/passwd"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- `create_rule(rule_definition)`: Create a new ruleFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.chown -R openhab:openhab /appFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.rm -rf /var/cache/apk/*Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.result = subprocess.run([Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for openhab-mcp-server@1.1.1 as of 17 h ago. This is the package itself, not its dependencies.
What would make this Verified
2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim openhab: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.