Wireshark MCP
Related Servers
Alternatives to Wireshark MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceAn MCP server for offline network forensic analysis and threat intelligence, enabling LLMs to analyze PCAP files, extract streams, detect threats, and identify credentials using tshark.6MIT
- AlicenseAqualityDmaintenanceA modular MCP server for analyzing PCAP files using protocol-specific analysis tools, enabling LLMs to read and analyze network packet captures from local paths or remote URLs.4MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI-assisted network packet analysis using Wireshark's TShark tool. It provides tools for pcap file overview, session extraction, protocol filtering, and statistical analysis through a standardized interface.1MIT
- FlicenseNot gradedqualityDmaintenanceAn automated security operations center MCP server that uses LLMs and network analysis tools like Tshark to detect threats in traffic data. It enables users to automatically ingest PCAP files, query specific packets, and generate intelligent security analysis reports.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server for analyzing network traffic and pcap files using tshark. It enables users to list TCP streams, extract application-layer payloads, and perform packet analysis with BPF filters.2-
- FlicenseBqualityCmaintenanceMCP server for network-troubleshooting PCAP analysis via tshark, enabling users to analyze PCAP files, detect anomalies, and troubleshoot network issues.22-
TDQS
Scored across 52 tools
Many tools overlap heavily: wireshark_aggregate ('primary statistics') competes with stats_protocol_hierarchy, stats_endpoints, stats_conversations, analyze_protocol, and stats_io_graph, and the seven detect_* security tools have fuzzy boundaries. The bracketed category tags ([Stats], [Security], [Forensics]) and open_file's recommendations help, but an agent can still easily misselect among the many statistics and anomaly tools.
Every tool uses the wireshark_ prefix with snake_case and a predictable verb/noun or category_noun structure (wireshark_capture, wireshark_stats_*, wireshark_detect_*, wireshark_extract_*). Deviations like the editcap_ subset are still consistent sub-groupings, and no mixed conventions appear.
52 tools far exceeds the 25+ threshold and lands in heavy territory, with obvious cruft like the deprecated wireshark_read_packets and the low-value wireshark_get_capabilities. The domain is genuinely broad, which partially justifies the size, but the surface is over-expanded and could be consolidated significantly.
Coverage is remarkably thorough: capture, filter, edit/split/trim, merge, stats, stream reassembly, decryption (TLS/WPA), export, forensics, and YARA scanning are all present, leaving essentially no dead ends for the pcap-analysis domain.