Is Zigbee2MQTT MCP safe to use?

Zigbee2MQTT MCP has an HVTrust score of 77.5/100 (Grade B), ranked #126 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Zigbee2MQTT MCP?

Zigbee2MQTT MCP scores 77.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 29 GitHub stars and is categorized under MCP Servers.

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

77.5/100

Rank #126 of 1320

Compare Zigbee2MQTT MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-04 · 0d ago

Recent change

Rank +6

Is Zigbee2MQTT MCP safe? Zigbee2MQTT MCP scores 77.5/100 (Grade B), ranked #126 of 1320 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.1/10; recent commits are unsigned; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#57 MikroMCP — 77.6 (B) → #58 Aiven MCP — 77.5 (B) → #60 Easy Notion MCP — 77.4 (B) → #61 MCP Zuul — 77.2 (B) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-04

Rank Moved

Rank dropped 12 spots (#114 → #126)

2026-08-31

Scorecard Added

OSSF Scorecard: 6.6/10

2026-08-31

Grade Changed

Trust grade C → B

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.1/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 Get email alerts for Zigbee2MQTT MCP View MCP Servers Report missing data

55.9

Activity sub-score · out of 100

#59

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 →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

Forks

Last Push

2026-09-04

today

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼12

was #114

Analysis

HVTrust Dimensions vs MCP Servers

77.5 / 100 · 100.0% confidence

Zigbee2MQTT MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

15.1 / 25

5.5 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.7 / 17

1.9 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

18.6 / 20

6.4 above avg 12.2

AdoptionLog-scaled stars · package downloads

6.1 / 20

in line with avg 6.3

Activity Inputs

55.9 / 100

StarsRepository reach

8.9 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

20.6 / 25

CommunityFork signal

1.4 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

6.1 / 10

OpenSSF Scorecard · scanned Sep 4, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 8

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 4

Is Zigbee2MQTT MCP safe?

Public supply-chain signals for Zigbee2MQTT MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Zigbee2MQTT MCP carries less obvious unverified-evidence risk than projects with thin signals.

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?

Zigbee2MQTT MCP has an OpenSSF Scorecard score of 6.1/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 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

None detected

No clear plugin system or broad tool 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 Zigbee2MQTT 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-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

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

2026-09-04

Rank Moved

Rank dropped 12 spots (#114 → #126)

2026-08-31

Scorecard Added

OSSF Scorecard: 6.6/10

2026-08-31

Grade Changed

Trust grade C → B

2026-08-31

Rank Moved

Rank rose 164 spots (#271 → #107)

2026-08-31

HVTrust Changed

HVTrust up 13.7pts (64.6 → 78.3)

2026-08-29

Rank Moved

Rank dropped 14 spots (#266 → #280)

2026-08-28

Rank Moved

Rank rose 11 spots (#277 → #266)

2026-08-27

Rank Moved

Rank dropped 11 spots (#266 → #277)

2026-08-26

Rank Moved

Rank dropped 24 spots (#242 → #266)

2026-08-24

Grade Changed

Trust grade B → C

2026-08-24

Rank Moved

Rank dropped 19 spots (#223 → #242)

2026-08-22

Rank Moved

Rank rose 14 spots (#236 → #222)

2026-08-21

Grade Changed

Trust grade C → B

2026-08-21

Rank Moved

Rank rose 10 spots (#246 → #236)

2026-08-19

Rank Moved

Rank dropped 16 spots (#226 → #242)

2026-08-17

Grade Changed

Trust grade B → C

2026-08-17

Rank Moved

Rank rose 13 spots (#236 → #223)

2026-08-16

Rank Moved

Rank dropped 22 spots (#214 → #236)

2026-08-13

Rank Moved

Rank dropped 11 spots (#198 → #209)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-12

Rank Moved

Rank rose 20 spots (#218 → #198)

2026-08-10

Newly Listed

First tracked at rank #218

GitHub → npm: zigbee2mqtt-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON