Skip to main content
Glama
mikusnuz

iptime-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to iptime-mcp

No user-submitted related servers found.

    Related Servers

    • SmartThings Rules Copilot MCP

      WoongTs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying and managing SmartThings locations, devices, and rules through MCP tools, with security and confirmation safeguards.
      MIT

    • mikrotik-mcp

      vesact
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP 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.
      12 npm
      2
      Apache 2.0

    • OPNsense MCP Server

      smaniktahla
      A
      license
      Not graded
      quality
      C
      maintenance
      An 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.
      122 npm
      MIT

    • keenetic-mcp

      salatmaster
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP agents to control Keenetic routers via plain language, providing network monitoring, device management, and safe configuration changes with backup and read-only options.
      67 npm
      24
      MIT

    • OPNsense MCP Server

      lucamarien
      A
      license
      A
      quality
      B
      maintenance
      A secure MCP server for managing OPNsense firewalls through AI assistants. Provides 81 tools across system, firewall, network, DNS, DHCP, VPN, HAProxy, services, diagnostics, and security domains.
      81
      125 PyPI
      21
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target distinct actions, but iptime_status and iptime_read overlap slightly as both can retrieve router state, and iptime_capabilities vs iptime_list_operations could be confused by an agent looking for available operations. The descriptions clarify the differences enough that the set is mostly unambiguous.

    Naming Consistency4/5

    The iptime_ prefix and verb-oriented names like list_*, apply_change, and cancel_change form a clear pattern. The main deviations are noun-style commands (iptime_status, iptime_capabilities) and compound plan_* names, but they are still readable and predictable.

    Tool Count5/5

    Thirteen tools is well within the ideal range for a router management server, and each tool covers a distinct part of the workflow: session, discovery, read-only inspection, backup, planning, and safe application of changes. No tool feels redundant or missing.

    Completeness4/5

    The set covers session management, read-only inspection, backup, firmware/config-restore planning, and the apply/cancel workflow, which is a complete core lifecycle. Minor gaps exist such as no dedicated way to inspect a plan's detailed parameters or perform simple router actions like reboot, though these can be worked around via the general plan/read mechanisms.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources