Skip to main content
Glama
sandraschi

packetsniffer-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to packetsniffer-mcp

No user-submitted related servers found.

    Related Servers

    • Wireshark MCP Server

      mixelpixx
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with direct access to Wireshark network analysis capabilities, enabling AI-powered network troubleshooting, packet analysis, and network monitoring through a secure interface.
      13
      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

      andsopwn
      F
      license
      C
      quality
      D
      maintenance
      Enables LLMs to capture, analyze, and summarize network traffic using Wireshark CLI tools, supporting live capture, pcap analysis, and LLM-oriented summaries.
      76
      -

    • Wireshark MCP

      jayimu
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to analyze network traffic using Wireshark/tshark, providing packet statistics, protocol analysis, and anomaly detection through natural language interaction.
      68
      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

    B3.1/5.0

    Scored across 6 tools

    Disambiguation3/5

    Most tools target distinct concerns, but 'status' and 'packetsniffer_mcp_status_card' both expose server health (differing only in output format), and 'agentic_packetsniffer_mcp_workflow' has a vague, undefined purpose that overlaps conceptually with both chat and ops orchestration. An agent can mostly tell them apart, but the redundancy and the fuzzy workflow tool create real selection risk.

    Naming Consistency3/5

    All names are snake_case, but prefixing is inconsistent: three tools carry a 'packetsniffer'/'agentic_packetsniffer_mcp' namespace prefix while 'help', 'status', and 'chat' are bare, and the naming mixes workflow-style, health-style, and action-style conventions. Readable but not a predictable pattern.

    Tool Count4/5

    Six top-level tools is a reasonable, well-scoped surface for this server. However, 'packetsniffer_ops' is an over-consolidated mega-tool packing roughly 14 distinct operations, which pushes complexity into a single tool rather than the count itself.

    Completeness4/5

    The ops tool covers the sniffing lifecycle well: interface discovery, blocking/background capture, capture status, stop, PCAP decode and analysis, plus USB and Bluetooth payload extraction and diffing. Minor gaps remain (no live stream display, packet injection, or filter validation), but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources