Skip to main content
Glama
labeveryday

Network MCP Server

by labeveryday
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Network MCP Server

No user-submitted related servers found.

    Related Servers

    • SharkMCP

      tuliperis
      A
      license
      A
      quality
      F
      maintenance
      A Model Context Protocol server that provides network packet capture and analysis capabilities through Wireshark/tshark integration, enabling AI assistants to perform network security analysis and troubleshooting.
      4
      35
      MIT

    • toolkit-mcp-server

      cyanheads
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol server that provides LLM Agents with a comprehensive toolset for IP geolocation, network diagnostics, system monitoring, cryptographic operations, and QR code generation.
      5
      325 npm
      18
      Apache 2.0

    • WireMCP

      0xKoda
      A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that provides LLMs with real-time network traffic analysis capabilities, enabling tasks like threat hunting, network diagnostics, and anomaly detection through Wireshark's tshark.
      7
      585
      MIT

    • IR Toolshed MCP Server

      rossja
      A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server that provides network analysis tools for security professionals, enabling AI models like Claude to perform tasks such as ASN lookups, DNS analysis, WHOIS retrieval, and IP geolocation for security investigations.
      4
      1
      Apache 2.0
    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.8/5.0

    Scored across 34 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, such as DNS lookups (single vs batch), connectivity tests (ping, batch_ping, mtr, traceroute), pcap analysis (filter, custom filter, DNS, TCP issues, conversations, hierarchy, summary), and CIDR/VLAN operations. No two tools overlap in a way that would confuse an agent.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (e.g., dns_lookup, batch_ping, filter_packets, get_interfaces). There is no mixing of conventions or vague verbs, making the namespace predictable.

    Tool Count2/5

    With 34 tools, the count exceeds the 'too many' threshold of 25+ as per the rubric. While each tool serves a distinct purpose, the sheer number may overwhelm agents, and the server scope could be narrowed or grouped without losing functionality.

    Completeness5/5

    The tool surface covers the full lifecycle of network troubleshooting: DNS, ICMP, TCP, pcap analysis, CIDR planning, VLAN validation, system information, and more. There are no obvious gaps for the stated domain of network operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources