Skip to main content
Glama
Spiceman161

Keenetic NOC MCP

by Spiceman161

Related Servers

Alternatives to Keenetic NOC MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      A
      maintenance
      Enables AI agents to manage Keenetic routers through the same RCI API used by the router's web interface, working directly over the local network without cloud involvement. It supports reading device statuses and executing configuration changes, with confirm, dry-run, and destructive-action safeguards.
      23
      -
    • A
      license
      A
      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.
      18
      124 npm
      24
      MIT
    • A
      license
      C
      quality
      A
      maintenance
      Enables AI assistants to operate a DrayTek Vigor 3912S router through the full DrayOS CLI, with read-only tools by default and two-step confirm-gated writes. It also provides SQLite audit logging and safety controls like host-key pinning and command blocklists.
      217
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to monitor and securely manage AsusWRT and AsusWRT-Merlin routers via SSH with allowlisted commands, supporting read-only monitoring and controlled mutations.
      47
      2
      MIT

    TDQS

    A3.8/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools map cleanly to a resource and action, e.g. list_devices vs get_device and list_routes vs list_policies. A few pairs overlap: list_vpn vs get_vpn, list_interfaces vs get_interface vs get_wifi_status, and get_connection_status could be mistaken for internet connectivity rather than RCI reachability, though the descriptions do clarify these cases.

    Naming Consistency4/5

    The set mostly follows a predictable get_/list_ pattern where list_ means collections and get_ means a specific item or status. Minor deviations exist: list_vpn is singular while sibling tools are plural, and backup_config/rci_call use imperative verbs outside the get/list convention.

    Tool Count4/5

    19 tools is somewhat heavy, but the router domain genuinely spans devices, interfaces, VPN, Wi-Fi, routes, policies, DNS, logs, and configuration. The count is justified; only mild overlap between interface and VPN tools keeps it from being perfectly scoped.

    Completeness4/5

    The read-only monitoring surface is broad: internet, DNS, Wi-Fi, interfaces, VPN, routes, policies, devices, logs, and config backup. There is no dedicated restore/reboot/update tool, but the raw rci_call covers arbitrary commands, so the main gap is convenience operations rather than missing capability.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues