Home Assistant (vortitron) MCP Server
@vortitron/home-assistant-mcp
npm
v0.9.1
Published by @vortitron — 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.
Model Context Protocol (MCP) server that lets coding agents (Cursor, VS Code, Claude) read and control Home Assistant, ESPHome and Node-RED: inspect entities, call services, render templates, debug logs, edit automations and deploy Node-RED flows.
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 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. 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 Unconstrained path parameter "path" on "ha_read_config_file"MTC-CAP-008
Tool "ha_read_config_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.
Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.
Location: tool ha_read_config_file · inputSchema.properties.path
Tools 67
Each tool and what it can reach — statically extracted from the published source.
ha_read_config_filereads sensitive dataesphome_cleanno sensitive capabilityesphome_compileno sensitive capabilityesphome_dashboard_infono sensitive capabilityesphome_get_configno sensitive capabilityesphome_list_devicesno sensitive capabilityesphome_list_migrationsno sensitive capabilityesphome_logsno sensitive capabilityesphome_save_configno sensitive capabilityesphome_uploadno sensitive capability
Show 57 more tools ↓
esphome_validateno sensitive capabilityha_addon_install_vomeno sensitive capabilityha_call_serviceno sensitive capabilityha_check_configno sensitive capabilityha_clear_system_logno sensitive capabilityha_config_entry_optionsno sensitive capabilityha_config_flowno sensitive capabilityha_create_dashboardno sensitive capabilityha_delete_automationno sensitive capabilityha_delete_dashboardno sensitive capabilityha_delete_helperno sensitive capabilityha_fire_eventno sensitive capabilityha_get_automationno sensitive capabilityha_get_configno sensitive capabilityha_get_dashboardno sensitive capabilityha_get_entity_registryno sensitive capabilityha_get_error_logno sensitive capabilityha_get_historyno sensitive capabilityha_get_logbookno sensitive capabilityha_get_stateno sensitive capabilityha_get_supervisor_logno sensitive capabilityha_get_system_logno sensitive capabilityha_get_traceno sensitive capabilityha_integration_setup_vomeno sensitive capabilityha_list_areasno sensitive capabilityha_list_automationsno sensitive capabilityha_list_config_entriesno sensitive capabilityha_list_config_filesno sensitive capabilityha_list_dashboardsno sensitive capabilityha_list_devicesno sensitive capabilityha_list_discovery_flowsno sensitive capabilityha_list_entitiesno sensitive capabilityha_list_helpersno sensitive capabilityha_list_servicesno sensitive capabilityha_list_tracesno sensitive capabilityha_reload_automationsno sensitive capabilityha_render_templateno sensitive capabilityha_save_dashboardno sensitive capabilityha_set_automationno sensitive capabilityha_set_helperno sensitive capabilityha_set_log_levelno sensitive capabilityha_supervisor_apino sensitive capabilityha_trigger_automationno sensitive capabilityha_write_config_fileno sensitive capabilitynodered_create_flowno sensitive capabilitynodered_delete_flowno sensitive capabilitynodered_get_flowno sensitive capabilitynodered_get_flowsno sensitive capabilitynodered_list_nodesno sensitive capabilitynodered_set_flowsno sensitive capabilitynodered_update_flowno sensitive capabilityvomehome_create_instanceno sensitive capabilityvomehome_get_instanceno sensitive capabilityvomehome_get_login_urlno sensitive capabilityvomehome_list_instancesno sensitive capabilityvomehome_reboot_instanceno sensitive capabilityvomehome_use_instanceno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (67 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 3
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 |
|---|---|---|---|---|
v0.9.1 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-07 |
v0.7.0 |
A 99/100 | 0 | 1.13.0 | 2026-09-04 |
v0.4.5 |
A 99/100 | 0 | 1.13.0 | 2026-09-01 |
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 @vortitron/home-assistant-mcp --onlineOther implementations of Home Assistant 4
Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →
Enable Cursor, VS Code, Claude Code or any MCP-enabled IDE to help you vibecode and manage Home Assistant: create automations, design dashboards, tweak themes, modify configs, and deploy changes using natural language
Control your Home Assistant smart home devices using Claude. Runs locally on your machine with complete privacy
A Model Context Protocol Server for Home Assistant
Security scan results for the Home Assistant (oleander) MCP server.
More in Developer Tools
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.