Wireshark-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_pcapsB | List PCAP files in the specified directory. |
| load_pcapB | Load a PCAP file for analysis and return a session ID. |
| close_sessionA | Close and clean up a PCAP analysis session. |
| summary_statsB | Get summary statistics for a loaded PCAP session. |
| quick_triageA | One-shot triage for a PCAP: protocol overview, top talkers, IOC hints, and recommended next analysis tracks. Accepts session_id or pcap_path. |
| analyze_lateral_movementA | One-shot lateral movement analysis for SMB/NTLM/RDP evidence. Accepts session_id or pcap_path. |
| auto_webshellA | One-shot webshell analysis: enumerate HTTP streams, detect tool family, extract/guess key, decrypt, and extract loot to workdir/loot. Accepts session_id or pcap_path. |
| solve_solar_challengeA | Solve the Solar traffic-analysis CTF task: extract CVE, forged username, malicious filename, run path, flag, JWT key, and compute final flag{md5(...)}. Accepts session_id or pcap_path. |
| run_tsharkC | Run a tshark command with specified arguments. Arguments are validated against a whitelist. |
| run_display_filterB | Apply a display filter to the loaded PCAP and return matching packets. |
| follow_tcp_streamC | Follow and extract the content of a TCP stream. |
| detect_suspiciousB | Detect suspicious activity in the loaded PCAP based on predefined rules. |
| extract_iocsB | Extract Indicators of Compromise (IOCs) from the loaded PCAP. |
| generate_timelineB | Generate a timeline of network events from the loaded PCAP. |
| export_objectsA | Export objects (files, certificates, etc.) from a PCAP based on protocol. Accepts session_id or pcap_path. |
| advanced_threat_detectionD | Perform advanced threat detection using behavioral analysis and pattern recognition. |
| search_patternsA | 【CTF必备】Search for patterns including CTF flags (flag{...}, CTF{...}) and custom regex. Use this when: 1) User asks to find flag, 2) User wants to search for specific patterns in traffic, 3) After following a TCP stream to search its content. |
| analyze_entropyA | 【CTF必备】Analyze Shannon entropy of data to detect encryption or compression. High entropy (>5.0) suggests encrypted data. Use this when: 1) User suspects encrypted payload, 2) After finding suspicious data that looks random, 3) Before attempting decryption. |
| decode_streamA | 【CTF必备】Automatically decode Base64, hex, URL, or rot13 encoded data. Use this when: 1) User asks to decode something, 2) After entropy analysis suggests encoding, 3) Found what looks like encoded flag. |
| detect_webshellA | 【Webshell专用】Detect encrypted webshell traffic (Behinder, Godzilla, AntSword) using fingerprint matching. Use this when: 1) User asks about webshell, 2) Suspicious HTTP traffic found, 3) Encrypted POST data detected. |
| extract_webshell_keyA | 【Webshell专用】Extract decryption key from webshell handshake traffic. Use this when: 1) After detect_webshell finds encrypted traffic, 2) User knows the webshell type and wants to decrypt, 3) Found potential key exchange in first request. |
| decrypt_webshellA | 【Webshell专用】Decrypt webshell traffic to reveal attacker commands. Supports Behinder (AES), Godzilla (AES+XOR), AntSword (XOR). Use this when: 1) Key has been extracted, 2) User provides the key, 3) Want to see what commands attacker executed. |
| brute_force_webshellA | 【Webshell专用】Brute force webshell decryption key using common passwords. Use this when: 1) Key extraction failed, 2) Decryption with known key failed, 3) Need to recover key from encrypted traffic. |
| get_top_talkersA | Get Top-N communicating pairs by traffic volume. Use this when: 1) User wants to see who talks most, 2) Identifying C2 servers, 3) Finding data exfiltration targets. |
| detect_port_scanA | Detect port scanning behavior from traffic patterns. Use this when: 1) User suspects reconnaissance, 2) Many connections to different ports, 3) Early stage of attack analysis. |
| analyze_timingA | Analyze timing patterns to detect beaconing or periodic communication. Use this when: 1) User suspects C2 heartbeat, 2) Looking for automated callbacks, 3) Anomaly detection in time series. |
| capture_packetsA | 【实时抓包】Capture live traffic and provide raw packet data as JSON. Use this when: 1) User wants to capture live network traffic, 2) Monitoring current network activity, 3) Real-time threat detection. |
| capture_summaryA | 【实时抓包】Capture live traffic and provide protocol hierarchy statistics. Use this when: 1) User wants protocol distribution, 2) Quick network overview, 3) Traffic analysis summary. |
| capture_conversationsA | 【实时抓包】Capture live traffic and provide TCP/UDP conversation statistics. Use this when: 1) User wants conversation details, 2) Identifying communicating pairs, 3) Network mapping. |
| check_ip_threatA | 【威胁情报】Check an IP address against URLhaus blacklist. Use this when: 1) User asks if an IP is malicious, 2) Checking IOCs, 3) Threat intelligence lookup. |
| extract_credentialsA | 【取证分析】Extract credentials (HTTP Basic, FTP, Telnet, Kerberos) from a PCAP file. Use this when: 1) User wants to find passwords, 2) Credential harvesting analysis, 3) Forensic investigation. |
| extract_ntlm_hashesB | 【RDP/SMB取证】Extract NTLM hashes from SMB/RDP authentication traffic. Supports Hashcat and John the Ripper formats. Accepts session_id or pcap_path. |
| decrypt_rdpA | 【RDP取证】Analyze RDP sessions and correlate with NTLM evidence (NLA/TLS detection and handshake hints). Does not guarantee full TLS/CredSSP decryption. Accepts session_id or pcap_path. |
| analyze_rdp_attack_chainA | 【自动化攻击链路】Automated analysis of RDP + NTLM attack chain. Correlates NTLM evidence with RDP sessions and extracts forensic hints. Accepts session_id or pcap_path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| traffic-analysis | Comprehensive network traffic analysis with detailed protocol breakdown and security assessment |
| malware-analysis | Focused analysis for identifying malware communication patterns, C2 channels, and data exfiltration |
| network-forensics | Comprehensive forensics analysis to reconstruct network events and determine scope of compromise |
| advanced-threat-hunting | Sophisticated analysis for identifying advanced persistent threats, behavioral anomalies, and stealthy attacks |
| investigate_pcap | 【CTF/取证专用】系统性地调查 PCAP 文件,自动寻找 Flag、解密 Webshell、分析攻击链。提供标准调查流程和工具调用指导。 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 34 tools
Multiple tools overlap in purpose, especially in the webshell and detection categories (detect_webshell vs. auto_webshell vs. analyze_webshell; detect_suspicious vs. detect_port_scan vs. advanced_threat_detection). Also quick_triage overlaps with summary_stats and get_top_talkers, and analyze_lateral_movement overlaps with analyze_rdp_attack_chain and extract_ntlm_hashes. The descriptions help, but the boundaries remain unclear.
Most tools follow a verb_noun pattern (detect_, analyze_, extract_, capture_, run_, list_), but there are notable outliers like advanced_threat_detection, quick_triage, auto_webshell, and summary_stats which use adjective or noun forms. The mixed style is still readable and largely predictable, but not fully consistent.
34 tools is on the heavier side, especially with several highly specific CTF/webshell utilities (solve_solar_challenge, brute_force_webshell). However, the domain is complex and warrants a broad toolkit, so the count is not excessive but feels bloated with overlapping features.
The server covers a wide range of traffic analysis, live capture, IOC extraction, credential harvesting, webshell decryption, and RDP/NTLM forensics. Gaps are minor, such as no direct packet modification or a dedicated tool for listing loaded sessions, but core workflows are well supported.