Zigbee2MQTT MCP
MCP server for administering a Zigbee2MQTT estate: health reporting, mesh diagnostics, OTA updates, pairing, binding and device options over the MQTT bridge API.
Is Zigbee2MQTT MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Zigbee2MQTT MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Zigbee2MQTT MCP scores 70.0/100 (Grade B), ranked #330 of 1325 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 5.8/10; recent commits are unsigned; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Zigbee2MQTT MCP compares in MCP Servers
- #195 NotebookLM MCP 70.4 +0.4
- #196 SportIQ MCP 70.2 +0.2
- #197 Zigbee2MQTT MCP 70.0 this agent
- #198 ZulipChat MCP Server 70.0 ±0
- #199 Qiskit Code Assistant MCP Server 70.0 ±0
Bars show each HVTrust score; the tick marks Zigbee2MQTT MCP’s 70.0.
Where the 70.0 comes from
HVTrust dimensions vs the MCP Servers average
70.0 / 100 · 100.0% confidenceZigbee2MQTT MCP MCP Servers average (775 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
35.4 / 100Supply Chain Trust
Common questions about Zigbee2MQTT MCP
Does Zigbee2MQTT MCP publish package provenance?
Does Zigbee2MQTT MCP have an OpenSSF Scorecard?
Is Zigbee2MQTT MCP actively maintained?
What license does Zigbee2MQTT MCP use?
Are Zigbee2MQTT MCP's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/zigbee2mqtt-mcp)
<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
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