Skip to main content
Glama
weirdmachine64

SharkMCP

by weirdmachine64
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to SharkMCP

No user-submitted related servers found.

    Related Servers

    • 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
      -

    • 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

      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.
      69
      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

    B3.4/5.0

    Scored across 30 tools

    Disambiguation5/5

    Each tool targets a distinct operation on packet capture data, such as loading, listing, extracting fields, following streams, or computing statistics. Overlaps like io_stats and iograph are clarified by descriptions (one simple counts, the other multi-line graphs). No two tools appear to do the same thing.

    Naming Consistency3/5

    Tool names mix verb_noun patterns (list_pcaps, load_pcap, set_preference) with noun-only names (protocol_hierarchy, voip_calls, rtp_streams). While the naming is readable and uses snake_case consistently, the lack of a uniform verb prefix creates inconsistency.

    Tool Count4/5

    30 tools cover a broad range of PCAP analysis features (loading, filtering, statistics, protocol details, export). This is slightly above the typical 15-20 but justified given the extensive functionality of Wireshark/sharkd. No obvious bloat.

    Completeness5/5

    The tool surface is comprehensive for analyzing packet captures: it covers file management, packet listing, field extraction, stream reassembly, export objects, multiple statistics taps, protocol-specific analysis, preferences, and validation. Missing features like live capture or saving are outside the server's stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources