Wireshark MCP vs Reversecore MCP
A side-by-side look at the Wireshark MCP and Reversecore MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Wireshark MCP for security work as a local process; choose Reversecore MCP for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Wireshark MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
wireshark_get_capabilities, wireshark_get_file_info, wireshark_merge_pcaps.
Choose Reversecore MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You want tools like
audit_source_code, run_file, copy_to_workspace.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 67/100 · Great | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 338 | 212 |
| Directory activity | 7 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 52 | 114 |
| Full listing | View Wireshark MCP | View Reversecore MCP |
Tools & capabilities
Wireshark MCP tools 52
wireshark_get_capabilitiesGet Wireshark suite capabilities for this MCP server instance (available tools and versions).wireshark_get_file_infoGet capture file metadata (type, packet count, duration, size) via capinfos.wireshark_merge_pcapsMerge multiple capture files into one. input_files: comma-separated paths.wireshark_text2pcap_importConvert ASCII or hex dump into a capture file using text2pcap. encapsulation: link-layer type (default: ether).wireshark_list_interfacesList available network interfaces for capture.wireshark_captureCapture live network traffic. capture_filter: BPF syntax. ring_buffer: "filesize:1024,files:5".wireshark_filter_saveFilter packets from a pcap and save to a new file using a Wireshark display filter.wireshark_editcap_trimTrim capture to a timestamp window. Times in editcap format.wireshark_editcap_splitSplit a capture into smaller files by packet count or interval.wireshark_editcap_time_shiftAdjust all packet timestamps by a positive or negative offset in seconds.wireshark_editcap_deduplicateRemove duplicate packets within a sliding window (default: 5 packets).wireshark_aggregate[Primary statistics] Full-filter counts, groups, distinct values, numeric metrics, top-k, and time buckets. Field lists are comma-separated.- +40 more on the listing page
Reversecore MCP tools 114
audit_source_codePerform a security audit on a source code file (SAST). This tool analyzes source code (C, C++, Python, Go, etc.) to identify potential security vulnerabilities such as buffer overflows, injection flaws, and weak cryptography. It provides a structured breakdown of dangerous patterns found in the code to guide deeper manual or AI-driven analysis. Use this tool when you have access to original source code or when you want to analyze decompiled output exported to a file.run_fileIdentify file metadata using the ``file`` CLI utility.copy_to_workspaceCopy any accessible file to the workspace directory. This tool allows copying files from any location (including AI agent upload directories) to the workspace where other reverse engineering tools can access them. Supports files from: - Claude Desktop uploads (/mnt/user-data/uploads) - Cursor uploads - Windsurf uploads - Local file paths - Any other accessible locationcreate_directoryCreate a new sub-directory within the workspace. This tool allows AI agents to dynamically create isolated sub-workspaces for different tasks or sessions.list_workspaceList all files in the workspace directory. Returns: ToolResult with list of files in workspacescan_workspaceBatch scan all files in the workspace using multiple tools in parallel. This tool performs a comprehensive scan of the workspace to identify files, analyze binaries, and detect threats. It runs 'run_file', 'parse_binary_with_lief', and 'run_yara' (if rules exist) on all matching files concurrently. **Workflow:** 1. Identify files matching patterns (default: all files) 2. Run 'file' command on all files 3. Run 'LIEF' analysis on executable files 4. Run 'YARA' scan if rules are available 5. Aggregate results into a single reportexplain_patchAnalyze differences between two binaries and explain changes in natural language. This tool combines binary diffing with decompilation to help understand security patches. It identifies changed functions, decompiles them, and uses heuristics to explain the nature of the changes (e.g., "Added bounds check", "Replaced unsafe API").assemble_instructionsAssemble assembly instruction strings into raw machine byte values using Keystone.create_memory_sessionCreate a new memory session to store memories. Use this when starting a new reverse engineering analysis. The session name should be descriptive and follow a template format like 'malware_analysis_2024_001' or 'game_cheat_detection'.save_memory_itemSave important information to long-term memory. Use this to remember: - Function addresses and their purposes - Vulnerability patterns discovered - API call sequences - User instructions and preferences - Interesting strings or structuresrecall_memory_itemSearch and recall memories from past analyses. Use this when you need to remember something from earlier, or when the user asks about previous findings.list_memory_sessionsList all analysis sessions with timestamps and status. Use this to see what analyses have been done before, or to find a session to resume.- +102 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Wireshark MCP
{
"mcpServers": {
"bx33661-wireshark-mcp": {
"command": "uvx",
"args": [
"wireshark-mcp"
]
}
}
}
Reversecore MCP
{
"mcpServers": {
"reversecore-mcp": {
"command": "uvx",
"args": [
"reversecore-mcp"
]
}
}
}
Frequently asked questions
Wireshark MCP is categorized under Security and uses a local stdio subprocess. Reversecore MCP belongs to Security and uses a local stdio subprocess. Pick Wireshark MCP for security work and Reversecore MCP for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Wireshark MCP is listed as free. Auth: no auth required. Reversecore MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add bx33661-wireshark-mcp and reversecore-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Wireshark MCP has a quality signal of 67/100 (Great) with 7 views, 0 installs and 338 GitHub stars. Reversecore MCP has 63/100 (Good) with 2 views, 0 installs and 212 GitHub stars.