Skip to main content
Glama
noor202401938-netizen

packet-chef-mcp

by noor202401938-netizen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to packet-chef-mcp

No user-submitted related servers found.

    Related Servers

    • Wireshark MCP — Packet

      tejaswipandey3931l-coder
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants and security analysts to inspect PCAP/PCAPNG captures through MCP tools or REST endpoints, reassembling TCP/UDP streams, extracting payload artifacts, detecting CTF flags, credential leaks and network anomalies, and generating formal PDF or Markdown forensic reports. Every finding is bound to exact frame numbers, timestamps and endpoints with SHA-256 deduplicated evidence provenance.
      MIT

    • pcap-mcp

      jiadewoer
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to securely investigate packet captures through Wireshark's tshark engine, with bounded tools for protocol inventory, TCP failure diagnosis, latency measurement, and threat hunting.
      12
      MIT

    • Wireshark MCP

      bx33661
      A
      license
      C
      quality
      B
      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.
      54
      741 PyPI
      358
      MIT
    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.7/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct packet-analysis task: high-level summary/list versus protocol-specific extraction versus detection versus export. The only mild conceptual overlap, packet_summary and packet_list, is clearly resolved by their descriptions.

    Naming Consistency4/5

    All names use snake_case with a consistent packet_ prefix, which makes the set easy to scan. Some names are verb-led (packet_extract_*, packet_detect_*) while others are noun-led (packet_summary, packet_entropy, packet_ja3_fingerprints), so the pattern is slightly mixed.

    Tool Count5/5

    15 tools is at the top of the recommended range but each covers a distinct packet-analysis capability, from triage to protocol extraction to detection to export. There are no redundant placeholder tools or obviously missing core functions.

    Completeness4/5

    The surface covers core PCAP triage, extraction (DNS/HTTP/TLS/QUIC/WebSocket), detection (beacons/DNS tunneling), credentials, entropy, filtering, and Zeek export. It warns about unparsed enterprise protocols such as SMB, Kerberos, and SSH but offers no extraction tools for them, which is a minor workaround gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources