iptime-mcp
Related Servers
Alternatives to iptime-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI copilots and autonomous agents to inspect, diagnose, and safely manage TP-Link 4G/LTE gateways and broadband routers through typed MCP tools for status, signal, clients, Wi-Fi, DNS, SMS/USSD, and guarded mutations. It provides session leasing and confirmation safeguards to avoid locking out admins or disconnecting active sessions.MIT
- AlicenseNot gradedqualityAmaintenanceTurns a MikroTik router into 310 MCP tools for AI-driven configuration over SSH, covering firewall, routing, VPN, and more.731 npm25MIT
- AlicenseBqualityBmaintenanceEnables AI assistants and terminal users to inspect and administer TP-Link routers through typed MCP tools, including live LTE signal and cell/band control, connected clients and DHCP reservations, Wi-Fi and LED settings, diagnostics, SMS/USSD, and guarded disruptive actions.39MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying and managing SmartThings locations, devices, and rules through MCP tools, with security and confirmation safeguards.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for managing MikroTik RouterOS fleets, exposing 65+ tools for system administration, interfaces, firewall, DHCP/DNS, PPP, diagnostics, and SSH command execution with KeePass-backed credentials.10 npm2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server for comprehensive OPNsense firewall management, enabling AI assistants to manage firewall rules, NAT, VLANs, and network diagnostics, plus execute SSH/CLI commands. Supports safety modes like read-only and dry-run for safe operation.151 npmMIT
TDQS
Scored across 13 tools
Most tools are clearly separated by lifecycle stage: plan, apply, cancel, list, and read-only discovery. Minor overlap exists between iptime_plan_change and the specialized firmware/config plan tools, and between iptime_read, iptime_status, iptime_capabilities, and iptime_list_operations, but descriptions make the boundaries understandable.
All tool names use a consistent iptime_ prefix and snake_case, which makes the set predictable. Most follow verb_noun patterns, with minor deviations such as iptime_status, iptime_login, iptime_logout, iptime_capabilities, and iptime_read.
The server has 13 tools, which is well within a focused and manageable range. Each tool appears to earn its place by covering a distinct part of the safe planning, authentication, discovery, and read-only operation lifecycle.
The surface covers the important router-management lifecycle: discovery, authentication, read operations, backup, planning, applying, cancelling, and listing plans, including critical firmware and restore flows. Minor gaps may exist around explicit plan inspection or firmware upload visibility, but core workflows appear covered.