# Home Assistant (npm · @foreverworks/mcp-home-assistant)

Read your Home Assistant's states, areas and history, and run its actions, approving locks first.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@foreverworks/mcp-home-assistant`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-foreverworks-home-assistant/foreverworks-mcp-home-assistant.md), [page](https://verifymcp.io/servers/com-foreverworks-home-assistant/foreverworks-mcp-home-assistant)

## Channel facts

- Registry: `npm`
- Package: `@foreverworks/mcp-home-assistant`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 7 of 23 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to foreverworks/mcps).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2028 tokens (~202/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Home Assistant MCP server?

Home Assistant runs locally as an npm package, launched with npx -y @foreverworks/mcp-home-assistant. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-foreverworks-home-assistant -- npx -y @foreverworks/mcp-home-assistant
```

### Cursor

```json
{
  "mcpServers": {
    "com-foreverworks-home-assistant": {
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-home-assistant"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-foreverworks-home-assistant": {
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-home-assistant"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-foreverworks-home-assistant -- npx -y @foreverworks/mcp-home-assistant
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-foreverworks-home-assistant": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@foreverworks/mcp-home-assistant"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-foreverworks-home-assistant --command npx --arg -y --arg @foreverworks/mcp-home-assistant
```

### Hermes

```yaml
mcp_servers:
  com-foreverworks-home-assistant:
    command: "npx"
    args: ["-y", "@foreverworks/mcp-home-assistant"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-foreverworks-home-assistant": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@foreverworks/mcp-home-assistant"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-foreverworks-home-assistant -t stdio -c npx -a -y @foreverworks/mcp-home-assistant
```

### Other

```json
{
  "mcpServers": {
    "com-foreverworks-home-assistant": {
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-home-assistant"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 79, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.88

### 2026-11-03 (score 68)

First indexed and scored.

## MCP tools (10)

### `call_action` (~336 tokens)

Run an action

Run a Home Assistant action (formerly a service call): light.turn_on, climate.set_temperature, media_player.volume_set, script.turn_on. Answers once it has run, with the states that changed. An action in a domain the user approves call by call (lock, alarm_control_panel, cover, valve unless configured otherwise), aimed at an entity of one, or a homeassistant action aimed wider than named entities, is refused here with needs_confirmation: use call_action_confirmed. An action Home Assistant runs only for administrators (every reload, homeassistant.restart and the like) is refused with needs_admin, without being sent, when this token's user is not one. Sent once: if the answer is outcome_unknown, read the entities (get_states) before running it again. Only what the user asks for: these act on a home.

Input parameters:

- `data` (object): The action's fields, as list_actions shows them: {"brightness_pct": 40}, {"temperature": 21.5}. Not the target.
- `domain` (string, required): The action's domain: light, switch, climate, lock, script, homeassistant, ...
- `return_response` (boolean): Ask for the data the action answers with (a weather forecast, a calendar's events); only for actions list_actions marks with response.
- `service` (string, required): The action within the domain: turn_on, set_temperature, unlock, ... (list_actions lists them).
- `target` (object): What the action acts on. Several kinds may be combined; an action that takes no target (homeassistant.reload_all, a script) leaves it out.

### `call_action_confirmed` (~238 tokens)

Run an action, with the user's approval

The same as call_action, for any action, and the user approves every call before it runs: the way to lock or unlock a door, arm or disarm an alarm, open or close a cover or a valve. Only when the user asked for that action. Acts outside the computer: the client asks the user to approve each call.

Input parameters:

- `data` (object): The action's fields, as list_actions shows them: {"brightness_pct": 40}, {"temperature": 21.5}. Not the target.
- `domain` (string, required): The action's domain: light, switch, climate, lock, script, homeassistant, ...
- `return_response` (boolean): Ask for the data the action answers with (a weather forecast, a calendar's events); only for actions list_actions marks with response.
- `service` (string, required): The action within the domain: turn_on, set_temperature, unlock, ... (list_actions lists them).
- `target` (object): What the action acts on. Several kinds may be combined; an action that takes no target (homeassistant.reload_all, a script) leaves it out.

### `get_states` (~100 tokens)

Get states

The current state of one or more entities, with their attributes (a light's brightness, a thermostat's target, a sensor's unit) and when the state last changed. An id Home Assistant does not know is listed under not_found; when none is known, the call fails with suggestions.

Input parameters:

- `attributes` (boolean): Include each entity's attributes.
- `entity_ids` (array, required): The entity ids, like light.kitchen (list_entities finds them).

### `health` (~100 tokens)

Health

Whether this server works with its Home Assistant: the version, whether it is RUNNING, its time zone (history and logbook times carry an offset), whether the WebSocket API signs in too, whose token it holds and whether that user is an administrator (if not, the tools that need one are listed), and how many entities each domain has. ok: false comes with the problem. Call it first, and whenever a call fails with unreachable or auth.

### `history` (~271 tokens)

State history

How entities' states changed over a window, from the recorder: for each entity its changes oldest first (the first is the state when the window opened), the newest limit of them. Default the last 24 hours; at most 31 days, and only as far back as the recorder keeps (10 days unless configured otherwise).

Input parameters:

- `attributes` (boolean): Include each change's attributes too (much larger).
- `end` (string): Where it ends; default now, with its offset: 2026-03-01T18:00:00+02:00 or 2026-03-01T16:00:00Z. health gives the instance's time zone.
- `entity_ids` (array, required): The entities, like sensor.living_room_temperature.
- `hours` (integer): Instead of start: this many hours before end (default 24).
- `limit` (integer): At most this many changes per entity, the newest (1-1000).
- `start` (string): Where the window starts; default the last `hours` before end, with its offset: 2026-03-01T18:00:00+02:00 or 2026-03-01T16:00:00Z. health gives the instance's time zone.

### `list_actions` (~125 tokens)

List actions

The actions (formerly services) Home Assistant offers. Without a domain, every domain with its action names; with one, each action's description, whether it takes a target, whether it answers with data, and its fields (type, options, an example). Domains whose actions the user approves call by call (lock, alarm_control_panel, cover, valve unless configured otherwise) are marked confirm, and actions only an administrator's token may run are marked needs_admin when this token's user is not one.

Input parameters:

- `domain` (string): Only this domain's actions, with their fields.

### `list_areas` (~111 tokens)

List areas

Every area (or one), with its floor, its devices and the entities in it: an entity's own area, else its device's, as Home Assistant's area pages show them. Disabled devices and entities are left out. Also counts what has no area. Its ids are what call_action takes as area_id and device_id.

Input parameters:

- `area` (string): Only this area, by its name or id.
- `entities` (boolean): List each area's entity ids, not only how many there are.

### `list_entities` (~170 tokens)

List entities

Find entities: one row each with entity_id, name, state, unit and area, in entity id order. Filter by domain (light, sensor, climate, ...), by area (its name or id), and by words that must all appear in the id, the name or the area. Use it to find the entity_id other tools take; get_states reads an entity's attributes.

Input parameters:

- `area` (string): Only entities in this area, by its name or id (list_areas lists them).
- `domain` (string): Only entities of this domain, like light or sensor.
- `limit` (integer): At most this many rows (1-1000).
- `search` (string): Words that must all appear in the entity id, its name or its area, ignoring case.

### `logbook` (~244 tokens)

Logbook

What happened over a window, as Home Assistant's logbook tells it: states that changed, automations and scripts that ran, and what caused each (a user, an action, an automation) where it knows. Oldest first, the newest limit of them. Optionally for one entity.

Input parameters:

- `end` (string): Where it ends; default now, with its offset: 2026-03-01T18:00:00+02:00 or 2026-03-01T16:00:00Z. health gives the instance's time zone.
- `entity_id` (string): Only this entity's entries.
- `hours` (integer): Instead of start: this many hours before end (default 24).
- `limit` (integer): At most this many entries, the newest (1-1000).
- `start` (string): Where the window starts; default the last `hours` before end, with its offset: 2026-03-01T18:00:00+02:00 or 2026-03-01T16:00:00Z. health gives the instance's time zone.

### `render_template` (~129 tokens)

Render a template

Render a Home Assistant template (Jinja) with its own states and helpers, for what no other tool answers in one call: "{{ states.light | selectattr('state', 'eq', 'on') | map(attribute='entity_id') | list }}", "{{ area_entities('kitchen') }}", "{{ now() }}". Rendering changes nothing. Home Assistant renders templates only for administrators: with another user's token this answers needs_admin without asking Home Assistant (health says which it is).

Input parameters:

- `template` (string, required): The template text.
- `variables` (object): Variables the template can use by name.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-foreverworks-home-assistant/foreverworks-mcp-home-assistant#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 68

## Common questions

### What is the Home Assistant MCP server?

Home Assistant is an MCP server listed in the public MCP registry as com.foreverworks/home-assistant. Read your Home Assistant's states, areas and history, and run its actions, approving locks first. This page covers its npm package (@foreverworks/mcp-home-assistant).

### Is the Home Assistant MCP server safe to use?

Home Assistant scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Home Assistant MCP server expose?

Home Assistant exposes 10 tools: call_action, call_action_confirmed, get_states, health, history, and 5 more. Their descriptions and schemas cost roughly 1,824 tokens of context every time the server is loaded.

### Is the Home Assistant MCP server still maintained?

Home Assistant is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Home Assistant MCP server under?

Home Assistant declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Home Assistant MCP server?

VerifyMCP ran 15 checks on Home Assistant, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Home Assistant: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@foreverworks/mcp-home-assistant
- Socket report: https://socket.dev/npm/package/@foreverworks/mcp-home-assistant
- Repository: https://github.com/foreverworks/mcps
- Website: https://foreverworks.github.io/mcps/servers/home-assistant/
- Changelog RSS feed: https://verifymcp.io/servers/com-foreverworks-home-assistant/foreverworks-mcp-home-assistant.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-foreverworks-home-assistant/foreverworks-mcp-home-assistant/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-foreverworks-home-assistant/foreverworks-mcp-home-assistant.json
- HTML version of this page: https://verifymcp.io/servers/com-foreverworks-home-assistant/foreverworks-mcp-home-assistant