Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Schimmilab/mqtt-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/schimmilab/mqtt-mcp-server/mqtt-mcp-server)<a href="https://agentmods.dev/mcp/schimmilab/mqtt-mcp-server/mqtt-mcp-server"><img src="https://agentmods.dev/badge/mcp/schimmilab/mqtt-mcp-server/mqtt-mcp-server/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/schimmilab/mqtt-mcp-server/mqtt-mcp-server"><img src="https://agentmods.dev/badge/mcp/schimmilab/mqtt-mcp-server/mqtt-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mqtt-mcp-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "mqtt-mcp-server": { "command": "uvx", "args": [ "mqtt-mcp-server" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 8 lines scan A 1c5cc3f582a6
mqtt-mcp-server is an MCP server published in the GitHub repository Schimmilab/mqtt-mcp-server (0 stars, last pushed 9d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
zigbee2mqtt-mcp
Administer a Zigbee2MQTT estate: health, mesh diagnostics, OTA, pairing, device management. Runs locally from the zigbee2mqtt-mcp npm package. Needs 5 environment variables to run.
shelly-mcp
MCP server for the entire Shelly smart-home ecosystem (Gen1-Gen4 + BLU) — local-first, with cloud fallback. Unofficial community project. Runs locally from the shelly-mcp Python package.
ccu-mcp
MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API. Runs locally from the ccu-mcp npm package. Needs 20 environment variables to run.
victron-tcp
MCP server for Victron Energy GX devices via Modbus TCP or MQTT. Runs locally from the victron-tcp npm package. Needs 6 environment variables to run.
larnitech-mcp
MCP server for Larnitech smart-home controllers over API2. Runs locally from the larnitech-mcp Python package.
washer-mcp
MCP server "washer-mcp" as configured in madhukeshm/lg-washer-mcp. Runs locally from the washer-mcp Python package.