Homeassistant (orellbuehler) MCP Server

@orellbuehler/homeassistant-mcp npm v0.8.0 Source verified

Published by orellbuehler — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

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.

Trust grade
A
100/100
Last scanned get badge →
Trust
A · 100/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 100/100

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 − 0 = 100. 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:

✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.

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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 43

Each tool and what it can reach — statically extracted from the published source.

  • add_energy_devicesno sensitive capability
  • add_zha_group_membersno sensitive capability
  • check_configno sensitive capability
  • create_lovelace_resourceno sensitive capability
  • create_zha_groupno sensitive capability
  • delete_automationno sensitive capability
  • delete_lovelace_resourceno sensitive capability
  • get_automation_configno sensitive capability
  • get_configno sensitive capability
  • get_energy_prefsno sensitive capability
Show 33 more tools ↓
  • get_entityno sensitive capability
  • get_error_logno sensitive capability
  • get_historyno sensitive capability
  • get_logbookno sensitive capability
  • get_traceno sensitive capability
  • get_trace_contextsno sensitive capability
  • list_areasno sensitive capability
  • list_devicesno sensitive capability
  • list_domainsno sensitive capability
  • list_entitiesno sensitive capability
  • list_eventsno sensitive capability
  • list_hacs_repositoriesno sensitive capability
  • list_labelsno sensitive capability
  • list_lovelace_resourcesno sensitive capability
  • list_registry_entitiesno sensitive capability
  • list_servicesno sensitive capability
  • list_tracesno sensitive capability
  • list_zha_groupableno sensitive capability
  • list_zha_groupsno sensitive capability
  • reloadno sensitive capability
  • remove_energy_devicesno sensitive capability
  • remove_hacs_repositoryno sensitive capability
  • remove_zha_groupno sensitive capability
  • remove_zha_group_membersno sensitive capability
  • rename_entityno sensitive capability
  • render_templateno sensitive capability
  • save_energy_prefsno sensitive capability
  • set_energy_grid_sourceno sensitive capability
  • set_energy_solar_sourceno sensitive capability
  • set_entity_enabledno sensitive capability
  • update_lovelace_resourceno sensitive capability
  • upsert_automationno sensitive capability
  • validate_energy_prefsno sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v0.8.0 latest A 100/100 0 1.13.0 2026-09-07
v0.7.2 A 100/100 0 1.12.1 2026-08-19
v0.7.1 A 100/100 0 1.12.1 2026-08-15

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.

MCP Trust Score: A · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/orellbuehler-homeassistant-mcp/badge.svg)](https://mcptrustchecker.com/registry/orellbuehler-homeassistant-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/orellbuehler-homeassistant-mcp"><img src="https://mcptrustchecker.com/registry/orellbuehler-homeassistant-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/orellbuehler-homeassistant-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 @orellbuehler/homeassistant-mcp --online

Use the free API → How scoring works

Other implementations of Homeassistant 3

Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →

More in Web, Search & Scraping