Skip to main content
Glama

Related Servers

Alternatives to tshark-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      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
    • 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
    • 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.
      -
    • 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
      -

    TDQS

    A3.9/5.0

    Scored across 34 tools

    Disambiguation4/5

    Nearly every tool has a clearly bounded job, and the descriptions actively route the agent ("for calls use sip_dialogs, for SMS over IMS sms_over_ims"; tcp_connections vs tcp_health; diameter_transactions vs diameter_sessions vs diameter_avps). The only real overlap is between the capture-overview family (pcap_info, capture_metadata, capture_quality, capture_index, incident_summary), where incident_summary explicitly says "start here" and calls the others, so an agent may hesitate over which entry point to use but not misselect a protocol tool.

    Naming Consistency4/5

    All names are snake_case and consistently descriptive: protocol tools are named resource-first (diameter_sessions, gtp_ies, dns_transactions, tls_handshakes) and action tools verb-first (filter_packets, find_fields, check_filter, open_capture, compare_captures). The mix of noun-phrase and verb_noun patterns is a minor deviation from a single convention, but it is predictable and never ambiguous.

    Tool Count3/5

    34 tools is above the comfortable range, but the surface is genuinely broad (Diameter, GTPv2-C, SIP/IMS, RTP, DNS, TLS, HTTP plus capture hygiene and cross-protocol correlation), and each tool appears to cover a distinct protocol+view. The meta-tools (incident_summary, trace_subscriber, roaming_attach_check, compare_captures) and open_capture handle caching help keep the set navigable, but it is still at the heavy end.

    Completeness4/5

    Coverage is unusually complete: capture discovery and indexing, quality/trust assessment, raw filter and per-frame fallbacks, filter authoring helpers, cause decoding, and deep per-protocol transaction/IE tools with cross-protocol subscriber tracing and A/B comparison. Remaining gaps are minor — no follow-stream payload extraction or export-objects tool, no dedicated PFCP or MAP transaction tool (only reachable through trace_subscriber/roaming_attach_check), and no decryption path for TLS/HTTP.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues