Homeassistant (robbrad) MCP Server
homeassistant-mcp
PyPI
v3.2.1
Published by robbrad — 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 using FastMCP
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 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Hardcoded JSON Web Token in test/example/packaging MTC-SRC-008 | exfiltration |
2. Client adoption risk — 99 − 4 = 95. 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 |
|---|---|
| −3 | capability blast radius (moderate) — 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.
Findings 1
low Hardcoded JSON Web Token in test/example/packaging (tests/property/test_security_properties.py)MTC-SRC-008
A hardcoded JSON Web Token (an embedded JSON Web Token (often an example or expired token)) appears in `tests/property/test_security_properties.py:151`. 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/property/test_security_properties.py
Tools 40
Each tool and what it can reach — statically extracted from the published source.
send_notificationnetwork egressalarm_controlno sensitive capabilityapi_infono sensitive capabilityautomation_controlno sensitive capabilitycalendar_accessno sensitive capabilitycall_serviceno sensitive capabilitycamera_controlno sensitive capabilitycamera_proxy_getno sensitive capabilityclimate_controlno sensitive capabilityconfig_checkno sensitive capability
Show 30 more tools ↓
cover_controlno sensitive capabilitydiscover_toolsno sensitive capabilityerror_log_getno sensitive capabilityevents_controlno sensitive capabilityfan_controlno sensitive capabilityhistory_queryno sensitive capabilityhumidifier_controlno sensitive capabilityinput_boolean_controlno sensitive capabilityinput_datetime_controlno sensitive capabilityinput_number_controlno sensitive capabilityinput_select_controlno sensitive capabilityinput_text_controlno sensitive capabilityintent_handleno sensitive capabilitylawn_mower_controlno sensitive capabilitylights_controlno sensitive capabilitylist_devicesno sensitive capabilitylock_controlno sensitive capabilitylogbook_queryno sensitive capabilitymedia_player_controlno sensitive capabilityscene_controlno sensitive capabilityscript_controlno sensitive capabilityservices_controlno sensitive capabilitysiren_controlno sensitive capabilitystates_controlno sensitive capabilityswitch_controlno sensitive capabilitytemplate_renderno sensitive capabilityvacuum_controlno sensitive capabilityvalve_controlno sensitive capabilitywater_heater_controlno sensitive capabilityweather_controlno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (40 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 |
|---|---|---|---|---|
v3.2.1 latest |
A 95/100 | 1 | 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 homeassistant-mcp --online --registry pypiOther implementations of Homeassistant 3
Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →
Model Context Protocol server for Home Assistant: introspect entities, services, events, registries, render templates and validate configuration to help AI agents author HA configs and automations.
Home Assistant Model Context Protocol Server
Home Assistant Model Context Protocol Server - Control your smart home through AI assistants
More 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