Zwave Js Ui MCP Server
mcp-server-zwave-js-ui
PyPI
v0.4.0
Published by cacack — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for Z-Wave device management via the zwave-js-server WebSocket exposed by Z-Wave JS UI
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 24
Each tool and what it can reach — statically extracted from the published source.
zwave_add_associationno sensitive capabilityzwave_association_groupsno sensitive capabilityzwave_associationsno sensitive capabilityzwave_begin_exclusionno sensitive capabilityzwave_begin_inclusionno sensitive capabilityzwave_begin_rebuilding_routesno sensitive capabilityzwave_controller_infono sensitive capabilityzwave_firmware_update_statusno sensitive capabilityzwave_list_nodesno sensitive capabilityzwave_node_configno sensitive capability
Show 14 more tools ↓
zwave_node_infono sensitive capabilityzwave_node_valuesno sensitive capabilityzwave_rebuild_node_routesno sensitive capabilityzwave_rebuild_routes_statusno sensitive capabilityzwave_reinterview_nodeno sensitive capabilityzwave_remove_associationno sensitive capabilityzwave_remove_failed_nodeno sensitive capabilityzwave_set_config_parameterno sensitive capabilityzwave_set_node_locationno sensitive capabilityzwave_set_node_nameno sensitive capabilityzwave_set_valueno sensitive capabilityzwave_stop_exclusionno sensitive capabilityzwave_stop_inclusionno sensitive capabilityzwave_stop_rebuilding_routesno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (24 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.4.0 latest |
A 99/100 | 0 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-server-zwave-js-ui --online --registry pypiMore in AI & Agents
Authenticated MCP transport with HTTP Signatures for AAuth agents
Local-first MCP server for parallel AI coding agents to claim file ownership before edits, preventing stomping on each other in the same worktree.
Agent-agnostic intercommunication system — sessions, messaging, channels, shared state, and real-time events
MCP server for AI agent task communication and delegation with diagnostic lifecycle visibility
Programmatic add/link/unlink for MCP servers across 23 AI coding agents (Claude Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, Zed, Cline, OpenCode, Goose, Kiro, Windsurf, and more). Functional API with dry-run support.
MCP server layer exposing agent-mesh orchestrator as an MCP agent