Home Assistant Blade MCP Server

home-assistant-blade-mcp PyPI v0.8.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Home Assistant MCP Server — entities, control, automations, history, energy, multi-site

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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
Moderate
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 = 95/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 − 5 = 95. 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:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 36

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

  • ha_webhooknetwork egress
  • ha_alarmno sensitive capability
  • ha_areasno sensitive capability
  • ha_automation_createno sensitive capability
  • ha_automation_deleteno sensitive capability
  • ha_automation_getno sensitive capability
  • ha_automation_toggleno sensitive capability
  • ha_automation_triggerno sensitive capability
  • ha_automationsno sensitive capability
  • ha_calendar_eventsno sensitive capability
Show 26 more tools ↓
  • ha_call_serviceno sensitive capability
  • ha_camera_snapshotno sensitive capability
  • ha_climateno sensitive capability
  • ha_configno sensitive capability
  • ha_devicesno sensitive capability
  • ha_entitiesno sensitive capability
  • ha_error_logno sensitive capability
  • ha_eventsno sensitive capability
  • ha_floorsno sensitive capability
  • ha_historyno sensitive capability
  • ha_infono sensitive capability
  • ha_labelsno sensitive capability
  • ha_lightno sensitive capability
  • ha_lockno sensitive capability
  • ha_logbookno sensitive capability
  • ha_notifyno sensitive capability
  • ha_sceneno sensitive capability
  • ha_script_runno sensitive capability
  • ha_searchno sensitive capability
  • ha_services_listno sensitive capability
  • ha_stateno sensitive capability
  • ha_statesno sensitive capability
  • ha_states_by_domainno sensitive capability
  • ha_statisticsno sensitive capability
  • ha_statistics_listno sensitive capability
  • ha_templateno sensitive capability

What this scan could not see

Versions 1

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 95/100 0 1.13.0 2026-08-25

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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/home-assistant-blade-mcp/badge.svg)](https://mcptrustchecker.com/registry/home-assistant-blade-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/home-assistant-blade-mcp"><img src="https://mcptrustchecker.com/registry/home-assistant-blade-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/home-assistant-blade-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 home-assistant-blade-mcp --online --registry pypi

Use the free API → How scoring works

More in Lifestyle & Local