Wireshark MCP Server

wireshark-mcp PyPI v3.0.0

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.

A production-grade Model Context Protocol (MCP) server for Wireshark

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

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 − 4 = 96. 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:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — 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 6

low Shell/command execution in packaging/dev tooling (homebrew/.github/scripts/generate_formula.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`homebrew/.github/scripts/generate_formula.py:89`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: dir, "bin", "pip") subprocess.run( [pip, "install", "--quiet", f"wireshark-mcp=={version}"], check=

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server homebrew/.github/scripts/generate_formula.py

low Shell/command execution in packaging/dev tooling (scripts/benchmark_analysis_paths.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/benchmark_analysis_paths.py:96`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: te=d"]) completed = subprocess.run(command, capture_output=True, text=True, check=False) if completed.returncode

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/benchmark_analysis_paths.py

low Shell/command execution in packaging/dev tooling (tests/test_field_names.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_field_names.py:43`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fter `-e`.""" out = subprocess.run(["tshark", "-G", "fields"], capture_output=True, text=True, timeout=120).stdout

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_field_names.py

low Shell/command execution in packaging/dev tooling (tests/test_prompt_cache.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_prompt_cache.py:78`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ] = seed proc = subprocess.run( [sys.executable, "-c", script], cwd=REPO_ROOT,

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_prompt_cache.py

low Shell/command execution in packaging/dev tooling (tests/test_server.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_server.py:506`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: s.close() proc = subprocess.Popen( [ sys.executable, "-m", "wireshark

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_server.py

low Shell/command execution in packaging/dev tooling (tests/test_skill_distribution.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_skill_distribution.py:51`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import sys res = subprocess.run( [sys.executable, str(ROOT / "scripts" / "sync_skills.py"), "--check"],

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_skill_distribution.py

Tools 34

Each tool and what it can reach — statically extracted from the published source.

  • wireshark_get_packet_bytesreads sensitive data
  • wireshark_aggregateno sensitive capability
  • wireshark_captureno sensitive capability
  • wireshark_decode_asno sensitive capability
  • wireshark_decrypt_tlsno sensitive capability
  • wireshark_decrypt_wpano sensitive capability
  • wireshark_editcap_deduplicateno sensitive capability
  • wireshark_editcap_splitno sensitive capability
  • wireshark_editcap_time_shiftno sensitive capability
  • wireshark_editcap_trimno sensitive capability
Show 24 more tools ↓
  • wireshark_extract_fieldsno sensitive capability
  • wireshark_extract_framesno sensitive capability
  • wireshark_filter_saveno sensitive capability
  • wireshark_flow_graphno sensitive capability
  • wireshark_follow_streamno sensitive capability
  • wireshark_get_capabilitiesno sensitive capability
  • wireshark_get_file_infono sensitive capability
  • wireshark_get_packet_contextno sensitive capability
  • wireshark_get_packet_detailsno sensitive capability
  • wireshark_get_packet_listno sensitive capability
  • wireshark_list_interfacesno sensitive capability
  • wireshark_merge_pcapsno sensitive capability
  • wireshark_open_fileno sensitive capability
  • wireshark_quick_analysisno sensitive capability
  • wireshark_read_packetsno sensitive capability
  • wireshark_search_packetsno sensitive capability
  • wireshark_set_protocol_prefsno sensitive capability
  • wireshark_stats_conversationsno sensitive capability
  • wireshark_stats_endpointsno sensitive capability
  • wireshark_stats_expert_infono sensitive capability
  • wireshark_stats_io_graphno sensitive capability
  • wireshark_stats_protocol_hierarchyno sensitive capability
  • wireshark_stats_service_response_timeno sensitive capability
  • wireshark_text2pcap_importno sensitive capability

What this scan could not see

Versions 3

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.

VersionScoreFindingsEngineScanned
v3.0.0 latest A 96/100 6 1.13.0 2026-09-06
v2.0.0 A 96/100 3 1.13.0 2026-08-25
v1.1.5 A 93/100 1 1.12.1 2026-07-27

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.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/wireshark-mcp/badge.svg)](https://mcptrustchecker.com/registry/wireshark-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/wireshark-mcp"><img src="https://mcptrustchecker.com/registry/wireshark-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/wireshark-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 pypi

Use the free API → How scoring works

More in Developer Tools