MQTT MCP Server
Enables interacting with MQTT brokers to publish, subscribe, and manage connections, with a real-time web UI for visual feedback.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
sergiudanstan
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
mqtt_connectConnect to an MQTT broker.
mqtt_publishPublish a message to an MQTT topic.
mqtt_subscribeSubscribe to an MQTT topic to receive messages.
mqtt_unsubscribeUnsubscribe from an MQTT topic.
mqtt_disconnectDisconnect from the MQTT broker.
mqtt_statusGet the current MQTT connection status.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
ws affected by a DoS when handling a request with many HTTP headers
ws: Memory exhaustion DoS from tiny fragments and data chunks
express vulnerable to XSS via response.redirect()
Express.js Open Redirect in malformed URLs
MQTT_BROKERmqtt://broker.hivemq.com:1883 MQTT_TOPIC=color/change PORT=3000 npm run start:webMQTT_TOPICMQTT_BROKER=mqtt://broker.hivemq.com:1883 =color/change PORT=3000 npm run start:webPORTTool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
6/6 tools missing one or more hints — mqtt_connect (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mqtt_publish (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mqtt_subscribe (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool inputs are validated
4/6 tool handlers declare input schemas (67%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool handlers catch errors
5/6 tool handlers wrap calls in try/catch (83%)
Wrap each tool handler body in try/catch and return a structured error response.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tests exist
No test files found
Add tests that exercise each declared tool.
Production dependencies are patched
0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.0.4 (high), ws@8.16.0 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/sergiudanstan/mqtt-mcp-server)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check