Wireshark MCP Server
wireshark-mcp
PyPI
v1.1.5
Published by bx33661 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Sensitive-source and external-sink co-existMTC-FLOW-004
Tools that read sensitive data ([wireshark_get_packet_bytes]) and tools that can send data out ([wireshark_filter_save]) are exposed together. An agent can move private data to the sink.
Evidence: sources [wireshark_get_packet_bytes] → sinks [wireshark_filter_save]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow wireshark_get_packet_bytes → wireshark_filter_save
Tools 32
Each tool and what it can reach — statically extracted from the published source.
wireshark_filter_savenetwork egresswireshark_get_packet_bytesreads sensitive datawireshark_captureno sensitive capabilitywireshark_decode_payloadno sensitive capabilitywireshark_editcap_deduplicateno sensitive capabilitywireshark_editcap_splitno sensitive capabilitywireshark_editcap_time_shiftno sensitive capabilitywireshark_editcap_trimno sensitive capabilitywireshark_extract_fieldsno sensitive capabilitywireshark_follow_streamno sensitive capability
Show 22 more tools ↓
wireshark_get_capabilitiesno sensitive capabilitywireshark_get_file_infono sensitive capabilitywireshark_get_packet_contextno sensitive capabilitywireshark_get_packet_detailsno sensitive capabilitywireshark_get_packet_listno sensitive capabilitywireshark_list_interfacesno sensitive capabilitywireshark_list_ipsno sensitive capabilitywireshark_merge_pcapsno sensitive capabilitywireshark_open_fileno sensitive capabilitywireshark_plot_protocolsno sensitive capabilitywireshark_plot_trafficno sensitive capabilitywireshark_quick_analysisno sensitive capabilitywireshark_read_packetsno sensitive capabilitywireshark_search_packetsno sensitive capabilitywireshark_security_auditno sensitive capabilitywireshark_stats_conversationsno sensitive capabilitywireshark_stats_endpointsno sensitive capabilitywireshark_stats_expert_infono sensitive capabilitywireshark_stats_io_graphno sensitive capabilitywireshark_stats_protocol_hierarchyno sensitive capabilitywireshark_stats_service_response_timeno sensitive capabilitywireshark_text2pcap_importno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (32 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.1.5 latest |
A 93/100 | 1 | 1.9.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan wireshark-mcp --online --registry pypiMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.