IoT-Edge-MCP-Server
Provides an MCP server for Industrial IoT/SCADA/PLC that unifies MQTT sensors/actuators and Modbus TCP/RTU device operations, with optional time-series storage (InfluxDB) and caching (Redis). Exposes MCP tools via HTTP endpoints using FastAPI (with /docs, /health, /metrics) for agent orchestration (e.g., PolyMCP). Includes a simulation mode for running without external hardware.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security-first design is claimed with API key + JWT, IP allowlisting, rate limiting, input validation, encryption (Fernet), HMAC signatures, and tamper-evident HMAC-chained audit logging. However, the README provides limited detail on TLS enforcement for the HTTP MCP endpoints themselves, the exact authorization model for tool/asset-level permissions, and how secrets are handled at runtime/logging beyond suggesting environment variables. Dependency hygiene/CVEs cannot be verified from the provided content.
⚡ Reliability
Best When
You need an MCP/agent-friendly control plane for mixed MQTT + Modbus industrial assets, and you can deploy with proper network isolation and production security settings.
Avoid When
You cannot enforce TLS, IP allowlisting, and authenticated access, or you need fine-grained authorization mapped to individual asset/command permissions.
Use Cases
- • AI agent orchestration for industrial monitoring (sensor reads, topology, system status)
- • Historical queries and aggregations over time-series sensor data (via InfluxDB, if configured)
- • Alarm management workflows (list active alarms, acknowledge)
- • Actuator control commands (e.g., valve/pump/motor/relay)
- • PLC integration via Modbus register/coil read-write
- • Development/testing using simulation mode without connecting real hardware
Not For
- • Untrusted, internet-facing deployments without TLS, strong authentication, and network controls
- • High-safety or safety-critical control without additional operational safeguards, validation, and human-in-the-loop review
- • Use cases requiring standardized enterprise IAM (e.g., SSO) out of the box
Interface
Authentication
README describes production auth as API key plus JWT bearer tokens and recommends environment variables for keys; explicit per-scope/permission model is not detailed.
Pricing
No pricing information provided; appears to be self-hosted software.
Agent Metadata
Known Gotchas
- ⚠ Tool invocations may have side effects (actuator commands, Modbus writes); agent retries without idempotency could cause unintended repeated actions.
- ⚠ Rate limits are mentioned but not fully specified in the visible README excerpt; agents may need backoff/queueing to avoid 429s.
- ⚠ MQTT optional TLS and Modbus network access require correct configuration; connection failures may surface as generic tool errors without standardized recovery guidance.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for IoT-Edge-MCP-Server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.