updated 2026-08-12 05:02 UTC

Zigbee2MQTT MCP

alexpfau/zigbee2mqtt-mcp

MCP server for administering a Zigbee2MQTT estate: health reporting, mesh diagnostics, OTA updates, pairing, binding and

MCP Servers TypeScript Grade B Listed MIT
65.7/100
Rank #218 of 1283
Compare Zigbee2MQTT MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-11 · 1d ago
Recent change
New

Is Zigbee2MQTT MCP safe? Zigbee2MQTT MCP scores 65.7/100 (Grade B), ranked #218 of 1283 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; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#62 Outline MCP Server — 65.8 (B) → #63 Intervals Icu MCP — 65.7 (B) → #65 ClickHouse — 65.4 (B) → #66 Testrail MCP Server — 65.3 (B) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Newly Listed
First tracked at rank #218
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Zigbee2MQTT MCP View MCP Servers Report missing data
55.2
Activity sub-score · out of 100
#64
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 B 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-08-12 05:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
22
Forks
1
Last Push
2026-08-11
yesterday
Commits (4 wk)
44
Downloads (7d)
1,484
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #218

Analysis

HVTrust Dimensions vs MCP Servers

65.7 / 100 · 100.0% confidence

Zigbee2MQTT MCP MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.5 / 25
2.5 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
18.5 / 20
6.1 above avg 12.4
AdoptionLog-scaled stars · package downloads
7.5 / 20
1.7 above avg 5.8

Activity Inputs

55.2 / 100
StarsRepository reach
8.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
20.6 / 25
CommunityFork signal
1.4 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
0%
of last 100 commits verified

Is Zigbee2MQTT MCP safe?

Zigbee2MQTT MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Zigbee2MQTT MCP publish package provenance?
Yes. Zigbee2MQTT MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Zigbee2MQTT MCP have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Zigbee2MQTT MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Zigbee2MQTT MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Zigbee2MQTT MCP use?
Zigbee2MQTT MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Zigbee2MQTT MCP's commits signed?
0% of the last 100 commits to Zigbee2MQTT 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
Zigbee2MQTT MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared 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

Maintain Zigbee2MQTT MCP?

For maintainers

HVTrust scores Zigbee2MQTT 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
Listed 1
2026-08-10
Newly Listed
First tracked at rank #218
GitHub → npm: zigbee2mqtt-mcp

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON