ha-mcp
PyPI
v8.4.3
Published by homeassistant-ai — 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.
Home Assistant MCP Server - Complete control of Home Assistant through MCP
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 − 4.2 = 96. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −4.2 | Hardcoded JSON Web Token in server code ×2 MTC-SRC-008 | exfiltration |
2. Client adoption risk — 96 − 7 = 89. 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 |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −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.
In the server's implementation (`src/ha_mcp/_vendor/websockets/cli.py:214`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: orm == "win32": os.system("") try: import readline # noqa: F401 except ImportError: # readlin
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/ha_mcp/_vendor/websockets/cli.py
In the server's implementation (`src/ha_mcp/_vendor/websockets/version.py:54`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: description = subprocess.run( ["git", "describe", "--dirty", "--tags", "--long"],
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/ha_mcp/_vendor/websockets/version.py
In the server's implementation (`src/ha_mcp/stdio_settings_sidecar.py:170`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: t + secret for the next spawn (best effort).""" try: _atomic_write_0600( _state_file(),
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/ha_mcp/stdio_settings_sidecar.py
In the server's implementation (`src/ha_mcp/utils/python_sandbox.py:386`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: bles) try: exec(expr, safe_globals, safe_locals) except (MemoryError, RecursionError): # Resour
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/ha_mcp/utils/python_sandbox.py
A hardcoded JSON Web Token (an embedded JSON Web Token (often an example or expired token)) appears in `src/ha_mcp/config.py:27`. Verify whether this is a real credential; if so, remove and rotate it.
Evidence: JSON Web Token: eyJh…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server src/ha_mcp/config.py
In the server's implementation (`src/ha_mcp/_vendor/websockets/imports.py:28`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: supported" module = __import__(source[level:], namespace, None, [name], level) return getattr(module, name) de
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/ha_mcp/_vendor/websockets/imports.py
A hardcoded JSON Web Token (an embedded JSON Web Token (often an example or expired token)) appears in `tests/test_constants.py:13`. Verify whether this is a real credential; if so, remove and rotate it.
Evidence: JSON Web Token: eyJh…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server tests/test_constants.py
In a packaging/dev/install script (shipped, but not the server runtime) (`src/ha_mcp/resources/skills-vendor/scripts/check_eval_cases.py:290`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rn try: r = subprocess.run([node, "-e", NODE_SRC], input=json.dumps(probes), capt
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/ha_mcp/resources/skills-vendor/scripts/check_eval_cases.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_env_manager.py:223`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: y: result = subprocess.run( cmd, env=env, cwd=Path(__file__).parent.parent, check=False
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/test_env_manager.py
In a packaging/dev/install script (shipped, but not the server runtime) (`src/ha_mcp/smoke_test.py:38`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: try: __import__(module_name) print(f" ✓ {module_name} ({description})") except I
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/ha_mcp/smoke_test.py
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 |
|---|---|---|---|---|
v8.4.3 latest |
B 89/100 | 10 | 1.13.0 | 2026-09-05 |
v8.4.1 |
B 89/100 | 10 | 1.13.0 | 2026-09-04 |
v8.4.0 |
B 89/100 | 10 | 1.13.0 | 2026-08-30 |
v8.3.0 |
B 89/100 | 9 | 1.13.0 | 2026-08-25 |
v8.2.0 |
B 89/100 | 9 | 1.12.1 | 2026-08-10 |
v8.1.1 |
B 89/100 | 9 | 1.12.1 | 2026-08-06 |
v8.0.0 |
B 89/100 | 6 | 1.12.1 | 2026-08-03 |
v7.14.2 |
B 89/100 | 6 | 1.12.1 | 2026-07-27 |
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.
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 ha-mcp --online --registry pypi
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
MCP server for controlling Home Assistant lights and managing scenes. Lights only by design for safety.
A Home Assistant MCP Server
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.