mcp-wireshark

mcp-wireshark is a Python-based MCP server that exposes Wireshark/tshark functionality to MCP-compatible AI clients. It can run live packet capture, read/analyze .pcap/.pcapng files, apply display filters, follow TCP/UDP streams, and export analysis results (e.g., JSON) via defined MCP tools.

Evaluated Mar 30, 2026 (22d ago)
Repo ↗ Infrastructure mcp wireshark tshark network-analysis pcap packet-capture python security-monitoring
⚙ Agent Friendliness
58
/ 100
Can an agent use this?
🔒 Security
30
/ 100
Is it safe for agents?
⚡ Reliability
29
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
70
Documentation
75
Error Messages
0
Auth Simplicity
95
Rate Limits
0

🔒 Security

TLS Enforcement
20
Auth Strength
10
Scope Granularity
0
Dep. Hygiene
60
Secret Handling
70

No authentication/authorization is described for the MCP server; exposing it to untrusted networks could be risky. It relies on external binaries (tshark/wireshark) and privileged capture permissions (e.g., wireshark group), which increases operational/security considerations. TLS/auth at the transport layer are not documented (MCP typically depends on client/server configuration). Secret handling is not discussed; configuration examples show env PATH overrides but no secret management guidance.

⚡ Reliability

Uptime/SLA
0
Version Stability
45
Breaking Changes
40
Error Recovery
30
AF Security Reliability

Best When

Used in a developer/admin workflow where an operator can install dependencies (tshark) and run the MCP server locally or within a controlled network environment.

Avoid When

Avoid exposing the MCP server broadly to untrusted networks or multi-tenant environments without additional access controls; avoid running it as a privileged process when only offline analysis is needed.

Use Cases

  • Investigate network incidents by capturing or analyzing packet traces
  • Help AI agents summarize pcaps and extract protocol-specific stats
  • Extract TCP/UDP stream payloads for further analysis
  • Convert packet data into structured JSON for downstream automation

Not For

  • Use in environments where running tshark/wireshark binaries is disallowed
  • Use cases requiring strong authentication/authorization for the MCP endpoint
  • Large-scale always-on production traffic analytics without performance/operational planning

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication mechanism is described in the README; access is likely controlled by local process/network exposure of the MCP server and the host permissions.

Pricing

Free tier: No
Requires CC: No

The package is distributed as a Python package (MIT license) and does not describe any paid service tiers in the provided content.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Requires tshark to be installed and on PATH (or configured) before tools will function
  • Live capture may require OS permissions (e.g., wireshark group membership on Linux)
  • Processing large pcaps/long captures can be slow or resource-intensive; agents should limit capture duration/filter scope

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-wireshark.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered