Skip to main content
Glama

Related Servers

Alternatives to mcpcap

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      An MCP server that enables LLMs to analyze pcap files by providing tools for packet dissection, stream following, and data extraction via tshark. It supports protocol hierarchy analysis, credential scanning, and threat intelligence checks on captured network traffic.
      52
      423 PyPI
      255
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server for offline network forensic analysis and threat intelligence, enabling LLMs to analyze PCAP files, extract streams, detect threats, and identify credentials using tshark.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI-assisted network packet analysis using Wireshark's TShark tool. It provides tools for pcap file overview, session extraction, protocol filtering, and statistical analysis through a standardized interface.
      1
      MIT
    • 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
      584
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An automated security operations center MCP server that uses LLMs and network analysis tools like Tshark to detect threats in traffic data. It enables users to automatically ingest PCAP files, query specific packets, and generate intelligent security analysis reports.
      -

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct protocol (DNS, DHCP, ICMP) or metadata (capinfos), with no overlap in purpose. An agent can easily select the correct tool based on the protocol of interest.

    Naming Consistency4/5

    Three tools follow the clear 'analyze_<protocol>_packets' pattern, but 'analyze_capinfos' deviates by using a utility name instead of a protocol. The shared 'analyze_' prefix keeps the naming mostly predictable.

    Tool Count5/5

    With 4 tools, the server is well-scoped for focused PCAP analysis. Each tool has a clear role and the count is appropriate for a niche protocol analyzer.

    Completeness3/5

    The set covers DNS, DHCP, and ICMP analysis plus metadata, but lacks support for other common protocols (e.g., TCP, UDP, ARP) and generic packet inspection. This creates notable gaps for general PCAP analysis, though the core three protocols are well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues