# io.github.jarahkon/hass-mcp-server

MCP server for full Home Assistant control — dashboards, files, automations, add-ons, and more

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 1.0.6
- **Author:** io.github.jarahkon
- **License:** Unknown
- **npm:** @jarahkon/hass-mcp-server
- **Source:** https://github.com/jarahkon/hass-mcp-server
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 114 days — stale; the grade is a claim about the present made from dated evidence

## Security scan

- **Status:** clean
- **Scanned:** 2026-06-13T12:03:41.366Z
- **Version scanned:** 1.0.10
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `ha_list_addons`
- `ha_addon_info`
- `ha_install_addon`
- `ha_start_addon`
- `ha_stop_addon`
- `ha_restart_addon`
- `ha_uninstall_addon`
- `ha_addon_options`
- `ha_system_info`
- `ha_check_config`
- `ha_create_backup`
- `ha_list_backups`
- `ha_restart_core`
- `ha_check_api`
- `ha_get_config`
- `ha_update_core_config`
- `ha_get_components`
- `ha_get_error_log`
- `ha_list_automations`
- `ha_get_automation`
- `ha_create_automation`
- `ha_update_automation`
- `ha_delete_automation`
- `ha_list_scripts`
- `ha_create_script`
- `ha_update_script`
- `ha_delete_script`
- `ha_list_scenes`
- `ha_create_scene`
- `ha_update_scene`
- `ha_delete_scene`
- `ha_list_helpers`
- `ha_create_helper`
- `ha_update_helper`
- `ha_delete_helper`
- `ha_list_dashboards`
- `ha_create_dashboard`
- `ha_update_dashboard`
- `ha_delete_dashboard`
- `ha_get_dashboard_config`

## Install

**Verdict: review** — Installable, but 1 thing to check first: The last scan is 114 days old — the evidence behind this verdict is dated.
**Cautions** (coverage gaps and advisories — never blocking)
- The last scan is 114 days old — the evidence behind this verdict is dated.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"hass-mcp-server\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@jarahkon/hass-mcp-server\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on your machine.
- Floor 41, ceiling 65 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.jarahkon%2Fhass-mcp-server
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.jarahkon%2Fhass-mcp-server/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.jarahkon%2Fhass-mcp-server
- HTML page: https://forgeregistry.com/registry/io.github.jarahkon%2Fhass-mcp-server
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.