Server data from the Official MCP Registry
MCP server for MQTT 5.0 brokers (publish, subscribe, topic discovery).
MCP server for MQTT 5.0 brokers (publish, subscribe, topic discovery).
The Eclipse Ditto MCP server is well-structured with proper authentication patterns and input validation. However, there are several credential handling concerns: environment variables containing sensitive tokens are read at module load time (allowing logging/interception), credentials are used to build httpx clients that persist across requests, and Bearer tokens are stored in plaintext in client headers without additional protection. The server's permissions (network_http, env_vars) are appropriate for its IoT digital twin integration purpose, but credential management practices should be hardened. Supply chain analysis found 5 known vulnerabilities in dependencies (1 critical, 3 high severity). Package verification found 1 issue (1 critical, 0 high severity).
4 files analyzed · 14 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Unverified package source
We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.
Set these up before or after installing:
Environment variable: MQTT_HOST
Environment variable: MQTT_PORT
Environment variable: MQTT_USERNAME
Environment variable: MQTT_PASSWORD
Environment variable: MQTT_USE_TLS
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-nagarjunr-mqtt": {
"env": {
"MQTT_HOST": "your-mqtt-host-here",
"MQTT_PORT": "your-mqtt-port-here",
"MQTT_USE_TLS": "your-mqtt-use-tls-here",
"MQTT_PASSWORD": "your-mqtt-password-here",
"MQTT_USERNAME": "your-mqtt-username-here"
},
"args": [
"eclipse-ditto-mcp-server"
],
"command": "uvx"
}
}
}From the project's GitHub README.
MCP (Model Context Protocol) servers for IoT platforms — giving AI agents read access to device registries, digital twins, and telemetry.
Each server is a standalone directory under this repo — its own pyproject.toml, uv.lock, Dockerfile, and mcp.json example config. No shared library layer: every server is independently runnable and dockerizable.
<server-name>/
├── <server-name>mcpserver.py # FastMCP server (single file)
├── pyproject.toml # own dependencies
├── uv.lock
├── Dockerfile
├── mcp.json # example MCP client config
└── README.md # tools, env vars, setup for this server
| Server | Platform | Status |
|---|---|---|
eclipse-ditto | Eclipse Ditto digital twins (open source; also compatible with Bosch IoT Things and other Ditto-based deployments) | ✅ |
mqtt | MQTT 5.0 — the standard IoT pub/sub protocol (any broker: Mosquitto, EMQX, HiveMQ, AWS IoT Core, etc.) | ✅ |
More planned: Azure IoT Hub.
cd <server-name>
uv sync
uv run <server-name>mcpserver.py
Each server directory has an mcp.json with a ready-to-use client config example (Claude Desktop / VS Code / any MCP client). Copy the relevant block into your client's config, filling in the environment variables described in that server's README.
overwrite=False) using conditional HTTP headers rather than check-then-set, so the safe path is race-free, not just the default. Delete tools, where a server needs them, require an explicit confirm=True — there is no bulk/cascading delete.MIT — see LICENSE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.