updated 2026-11-11 00:08 UTC

Ha MCP

Repository Website

Configure and automate Home Assistant with Claude, ChatGPT, and other AI assistants.

MCP Servers Python Listed MIT

Is Ha MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.6 / 10
Provenance Attested
Signed commits 41%
Last push today
Advisories None known
Compare Ha MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Ha MCP scores 88.7/100 (Grade A), ranked #51 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.6/10; 41% of recent commits are signed; no published advisory affects its latest release (ha-mcp); last pushed 2026-11-11. Every point is earned from checkable signals — never paid placement. How scoring works →

How Ha MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Ha MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/homeassistant-ai/ha-mcp, MIT, last pushed 2026-11-11. 41% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.6/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection4
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies8
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 1
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 8
    SAST 4
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 8

  3. Published packages Linked and attested

    • PyPI ha-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: ha-mcp 9.1.2. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-26 OSSF Scorecard: 5.9/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Ha MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Ha MCP compares in MCP Servers

  1. #10 Containers Kubernetes MCP Server 89.6 +0.9
  2. #11 SearXNG Search 88.9 +0.2
  3. #12 Ha MCP 88.7 this agent
  4. #13 Cap Js MCP Server 88.6 −0.1
  5. #14 KiCad MCP Pro 88.5 −0.2

Bars show each HVTrust score; the tick marks Ha MCP’s 88.7.

Where the 88.7 comes from

HVTrust dimensions vs the MCP Servers average

88.7 / 100 · 100.0% confidence

Ha MCP MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.8 / 25
7.0 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
14.1 / 17
1.8 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.7 above avg 12.3
AdoptionLog-scaled stars · package downloads
16.2 / 20
8.6 above avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-10-25
Rank Moved
Rank rose 11 spots (#53 → #42)
2026-10-23
Rank Moved
Rank dropped 10 spots (#42 → #52)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.6/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View MCP Servers Report missing data
85.1
Activity sub-score · out of 100
#12
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
6.6k
Forks
429
Last Push
2026-11-11
today
Commits (4 wk)
449
Downloads (7d)
196,503
pypi
HN mentions (30d)
—
Open Issues
8
Rank Change
=
was #51

Analysis

Activity Inputs

85.1 / 100
StarsRepository reach
22.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.2 / 20

Common questions about Ha MCP

Public supply-chain signals for Ha MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Ha MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Ha MCP publish package provenance?
Yes. Ha MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Ha MCP have an OpenSSF Scorecard?
Ha MCP has an OpenSSF Scorecard score of 6.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Ha MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Ha MCP use?
Ha MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Ha MCP's commits signed?
41% of the last 100 commits to Ha MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Ha MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Ha MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Ha MCP?

For maintainers

HVTrust scores Ha MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 4HVTrust 2Grade 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1Surface 1
2026-10-25
Rank Moved
Rank rose 11 spots (#53 → #42)
2026-10-23
Rank Moved
Rank dropped 10 spots (#42 → #52)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 545 spots (#584 → #39)
2026-09-23
HVTrust Changed
HVTrust up 53.1pts (34.7 → 87.8)
2026-09-22
Newly Listed
First tracked at rank #584
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-08-26
Scorecard Added
OSSF Scorecard: 5.9/10
2026-08-26
Grade Changed
Trust grade B → A
2026-08-26
Rank Moved
Rank rose 56 spots (#85 → #29)
2026-08-26
HVTrust Changed
HVTrust up 11.0pts (76.7 → 87.7)
GitHub → Website → PyPI: ha-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 88.7 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/ha-mcp.svg)](https://hvtracker.net/agents/ha-mcp)
HTML:
<a href="https://hvtracker.net/agents/ha-mcp"><img src="https://hvtracker.net/badge/ha-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON