SharkMCP
Related Servers
Alternatives to SharkMCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceA Model Context Protocol server that enables AI assistants to perform network packet analysis, capture, and security operations on a remote machine via Wireshark/tshark.101MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that integrates Wireshark's network analysis capabilities with AI systems like Claude, allowing direct analysis of network packet data without manual copying.32MIT
- AlicenseBqualityFmaintenanceA Model Context Protocol server that provides LLMs with real-time network traffic analysis capabilities, enabling tasks like threat hunting, network diagnostics, and anomaly detection through Wireshark's tshark.7587MIT
- 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
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to analyze PCAP files for network forensics using Wireshark/tshark, providing high-performance packet inspection, filtering, and protocol analysis through the Model Context Protocol.2MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that leverages Wireshark/Tshark for real-time and offline network traffic analysis, enabling AI assistants to capture, parse, and detect threats with automated scanning and threat intelligence.2MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: analyze_pcap_file handles static file analysis, manage_config deals with configuration management, and start_capture_session/stop_capture_session form a clear lifecycle for live captures. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern with snake_case (analyze_pcap_file, manage_config, start_capture_session, stop_capture_session). The naming is predictable and readable throughout the set.
With 4 tools, the server is well-scoped for packet capture and analysis. Each tool earns its place by covering distinct aspects: static analysis, configuration management, and live capture lifecycle. This is an appropriate number for the domain.
The tool set covers core workflows for packet analysis (static and live) with configuration reuse. Minor gaps exist, such as no direct tool for listing or managing saved capture sessions, but agents can work around this using existing tools like manage_config and stop_capture_session.