Skip to main content
Glama

Related Servers

Alternatives to portviewer

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables developers to inspect port occupancy with process details, scan common development ports, and terminate processes blocking a specified port via MCP tools.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for managing local dev ports on macOS. It enables AI agents to inspect listening ports, identify owning processes and parent chains, kill processes safely, wait for ports, and report LAN exposure.
      2 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables local Linux network diagnostics through MCP tools for status checks, device discovery, reachability tests, topology inspection, incident review, monitoring status, and label or declared-link management.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes Windows system introspection and control as MCP tools, enabling inspection of processes, threads, modules, handles, memory, services, network endpoints, drivers, windows, and file signatures, plus process launching and control.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI agent to manage local development environments over MCP by starting, stopping, and restarting applications and processes, reading logs with cursors, and inspecting or freeing listening ports. Exposes a fixed set of id- and port-based tools, so the agent can operate registered processes without running arbitrary commands.
      2 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables secure remote management of the platform through nine MCP tools over STDIO and HTTP, including terminal execution, service controls, and live status monitoring.
      297 npm
      MIT

    TDQS

    C2.8/5.0

    Scored across 30 tools

    Disambiguation3/5

    Many tools overlap heavily: list_tcp/list_tcp4/list_tcp6 and list_udp/list_udp4/list_udp6, is_port_used/is_tcp_port_used/is_udp_port_used, and find_port/find_tcp_port/find_udp_port/find_listening_port. The descriptions clarify the granularity, but an agent must carefully distinguish near-duplicate variants.

    Naming Consistency5/5

    All tool names use consistent snake_case and generally follow a verb_noun pattern (list_tcp, get_listening_ports, find_endpoint, kill_process, can_bind_udp). Minor singular/plural pairs like get_port_process/get_port_processes are predictable and intentional.

    Tool Count2/5

    30 tools is excessive for a port/process viewer, largely because many operations are expanded into protocol- and IP-version-specific permutations. This creates redundancy rather than distinct capability, making the surface heavy for the domain.

    Completeness5/5

    The tool set comprehensively covers listing, filtering, checking, finding, binding, free-port discovery, process inspection, process tree retrieval, and process termination for TCP/UDP and IPv4/IPv6. No obvious lifecycle or inspection operation for the stated port/process domain is missing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues