Skip to main content
Glama
Mohamedaslam227

WiFi PCAP Analyzer MCP

by Mohamedaslam227
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to WiFi PCAP Analyzer MCP

No user-submitted related servers found.

    Related Servers

    • PCAP MCP Server

      LissajousX
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables Wireshark-like PCAP analysis through tshark, providing tools for filtering packets, extracting protocol fields, drilling down into frames, session tracking, and timeline analysis for troubleshooting 5G, IMS/SIP, and network protocol issues.
      -

    • noc-pcap-mcp-server

      anthonylouschwank
      A
      license
      A
      quality
      B
      maintenance
      Enables LLM-based assistants to diagnose network problems from PCAP/PCAPNG packet captures, offering tools for capture summaries, TCP conversation analysis, security anomaly detection, and JSON-RPC extraction without requiring Wireshark.
      5
      MIT

    • 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

    • wireshark-mcp

      MrDadpool
      A
      license
      B
      quality
      B
      maintenance
      Enables local LLM clients to capture and analyze network traffic using Wireshark's CLI tools, providing packet summaries, protocol hierarchies, conversations, endpoints, expert info, and stream reassembly without shell access.
      12
      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

    A4.1/5.0

    Scored across 23 tools

    Disambiguation3/5

    Most tools are clearly separated into lifecycle, metadata, and packet-retrieval roles, and the descriptions are detailed about input types. However, dissect_packet and get_packet_by_number are explicit aliases, and several TCP/DNS retrieval tools overlap enough to create misselection risk.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern with predictable prefixes like load_, get_, set_, and filter_. Singular/plural noun choices are consistent with the returned data, and even the redundant get_packet_by_number is name-consistent.

    Tool Count3/5

    At 23 tools, the server sits in the heavy 16-25 range and is borderline appropriate for a full PCAP analyzer. The count is defensible given the breadth of metadata, validation, and Wi-Fi-specific retrieval features, but the duplicate dissection tool and overlapping retrieval variants mean it could be trimmed without losing capability.

    Completeness5/5

    The server covers capture lifecycle, decryption-key configuration, export, metadata and statistics, validation, timeline analysis, generic filtering, per-frame dissection, and Wi-Fi-specific client/AP/transaction views. No major operational gap is apparent for file-based WiFi packet-capture analysis.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources