Give any MCP assistant safe control of a real Home Assistant house: floors, rooms and live state, the household's own scenes, and service calls behind a physical-action gate that refuses anything which opens the house.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
HOME_ASSISTANT_TOKENAPI keyrequiredA Home Assistant long-lived access token (Home Assistant, your profile, Security, Long-lived access tokens, Create token). It carries the full rights of the account that minted it, so mint it from an…
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
call_serviceRun one Home Assistant service call, e.g. domain "light", service "turn_on", entity_idRun one Home Assistant service call, e.g. domain "light", service "turn_on", entity_id
No input schema was published for this tool.
home_overviewRead the whole house at once. Returns the Home Assistant version, the floors, and one entry per roomRead the whole house at once. Returns the Home Assistant version, the floors, and one entry per room
No input schema was published for this tool.
home-mcpNo description publishedThis tool published no description. Forge does not invent one.
list_entitiesList the entities in the house that can be read or acted on, each with `entity_id` (what you pass toList the entities in the house that can be read or acted on, each with `entity_id` (what you pass to
No input schema was published for this tool.
list_macrosList every scene and script in the house, each with `entity_id`, `name` and `kind` (scene or script).List every scene and script in the house, each with `entity_id`, `name` and `kind` (scene or script).
No input schema was published for this tool.
run_macroTurn a phrase like "good night", "movie time" or "away" into the scene or script this house actuallyTurn a phrase like "good night", "movie time" or "away" into the scene or script this house actually
No input schema was published for this tool.
5 of 6 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Give any MCP assistant safe control of a real Home Assistant house: floors, rooms and live state, the household's own scenes, and service calls behind a physical-action gate that refuses anything which opens the house.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
57 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+45 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.