Skip to main content
Glama
netdiag-server
by ZANYANBU

Related Servers

Alternatives to netdiag-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to debug local networks in plain language by pinging, sweeping subnets, tracing routes, resolving DNS, scanning ports, inspecting ARP tables and active connections, and checking URL reachability.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely troubleshoot networks through read-only tools for device inventory, interface status, VLAN paths, BGP neighbors, route lookups, and interface error detection. Integrates with Microsoft Copilot Studio and Teams for natural-language-driven network diagnostics.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to check the health of internet infrastructure and specific services, helping diagnose whether issues are local or external.
      3
      16 npm
      ISC
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI clients to diagnose a local network and host security posture across Windows, Linux, and macOS — device inventories, DNS hijack checks, WiFi link health, port exposure, firewall state, and layered connectivity triage — all returned in one bounded, platform-normalized JSON envelope. Every answer comes with a concrete next tool call, and mutating actions like Wake-on-LAN require an explicit dry-run confirmation token.
      31
      125 npm
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool maps to a distinct diagnostic layer or probe (interface listing, Wi-Fi, IP config, routing, ARP, DNS, ping, traceroute, port, HTTP), so boundaries are mostly crisp. The only mild overlap is the aggregate `diagnose` versus the individual probes it presumably invokes, but its 'identify failing layer and fix' framing distinguishes it.

    Naming Consistency4/5

    Most names follow a noun_noun or noun-phrase convention (wifi_signal, ip_config, dns_lookup, port_check, http_check, route_table, arp_table) with `interfaces` as a plain noun. `diagnose`, `ping`, and `traceroute` are verb/vague outliers, but they are conventional names for these utilities and remain readable.

    Tool Count5/5

    Eleven tools is well within the ideal 3-15 range and each covers a distinct layer or probe in a bottom-up network diagnosis workflow. Nothing feels redundant or missing at the count level.

    Completeness4/5

    The surface covers physical/data-link (interfaces, wifi_signal), network (ip_config, route_table, arp_table), transport (ping, traceroute, port_check), and application (dns_lookup, http_check) layers, plus an aggregate `diagnose`. Minor gaps exist—no active connection listing (netstat-equivalent), DHCP/lease info, or bandwidth/MTU test—but core diagnostic workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data