Wireshark MCP vs Guardvibe
A side-by-side look at the Wireshark MCP and Guardvibe 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 Guardvibe 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 Guardvibe 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
check_code, check_project, get_security_docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 67/100 · Great | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 338 | 6 |
| Directory activity | 7 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 52 | 39 |
| Full listing | View Wireshark MCP | View Guardvibe |
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
Guardvibe tools 39
check_codeAnalyze inline code for security vulnerabilities (OWASP Top 10, XSS, SQL injection, insecure patterns). Pass code as a string parameter. For scanning files on disk, use scan_file instead. Example: check_code({code: 'app.get(...)', language: 'javascript'})check_projectScan multiple files for security vulnerabilities and generate a project-wide security report with a security score. Use this for comprehensive security audits.get_security_docsGet security best practices and remediation guidance for a specific topic, framework, or vulnerability type. Covers OWASP Top 10, framework-specific hardening (Next.js, Supabase, Stripe), and secure coding patterns. Returns actionable guidance with code examples.check_dependenciesCheck npm, PyPI, or Go packages for known security vulnerabilities (CVEs) using the OSV database. Use this before adding new dependencies or to audit existing ones.scan_directoryScan all files in a directory on disk for security vulnerabilities. Pass a directory path — reads files from filesystem. Returns security score (A-F) and findings. Results may be truncated for large projects — check fileRanking in JSON output for top files. Example: scan_directory({path: './src'})scan_dependenciesParse a lockfile or manifest (package.json, package-lock.json, requirements.txt, go.mod) and check all dependencies for known CVEs via the OSV database. Reads the file directly. Use this after installing dependencies, during CI, or when auditing existing projects for vulnerable packages.scan_hallucinated_packagesDetect AI-hallucinated and slopsquatted packages in a repo — the supply-chain seam commodity SCA misses. OFFLINE (deterministic): flags phantom imports (a package imported in source but absent from every package.json — a classic LLM hallucination tell) and typosquats of popular packages. ONLINE (opt-in, default on; gracefully degrades offline): adds npm-registry truth — packages that return 404 (definitive hallucination) and brand-new low-download packages (slopsquat-registration pattern). Run on AI-generated code at PR time, before `npm install`. Pass online:false for a fully deterministic, air-gapped scan.scan_secretsScan files and directories for leaked secrets, API keys, tokens, and credentials. Detects high-entropy strings, known API key patterns (AWS, Stripe, OpenAI, GitHub, Supabase), exposed .env files, and missing .gitignore coverage. Returns findings with exact line numbers and remediation steps.scan_stagedScan git-staged files for security vulnerabilities before committing. Run this before every commit to catch issues early. No input needed — automatically reads staged files. Diff-aware by default: reports only issues on newly-staged lines (set diff_aware:false for whole staged files).compliance_reportMap security findings to compliance controls (SOC2, PCI-DSS, HIPAA, GDPR, ISO27001, EUAIACT). Scans a directory and groups issues by control. Output includes a summary section at the top; for large projects, findings are truncated to top 50. Use mode=executive for C-level summary. Example: compliance_report({path: '.', framework: 'SOC2'})export_sarifScan a directory and export results in SARIF v2.1.0 format for CI/CD integration (GitHub, GitLab, Azure DevOps). Returns JSON string.check_package_healthCheck npm packages for typosquat risk, maintenance status, adoption metrics, and deprecation. Use this before adding new dependencies to catch suspicious or risky packages.- +27 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"
]
}
}
}
Guardvibe
{
"mcpServers": {
"goklab-guardvibe": {
"command": "npx",
"args": [
"-y",
"guardvibe"
]
}
}
}
Frequently asked questions
Wireshark MCP is categorized under Security and uses a local stdio subprocess. Guardvibe belongs to Security and uses a local stdio subprocess. Pick Wireshark MCP for security work and Guardvibe 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. Guardvibe is listed as free. Auth: no auth required. 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 goklab-guardvibe 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. Guardvibe has 65/100 (Great) with 3 views, 0 installs and 6 GitHub stars.