Atlas / MCP servers / 0xkoda / Wire

WireSAFE

mcp/0xkoda/wire

An MCP for WireShark (tshark). Empower LLM's with realtime network traffic analysis capability

Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
7 7r · 0w · 0d
Transport
stdio
License
MIT
Stars
586
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

WireMCP is a Model Context Protocol (MCP) server designed to empower Large Language Models (LLMs) with real-time network traffic analysis capabilities. By leveraging tools built on top of Wireshark's tshark, WireMCP captures and processes live network data, providing LLMs with structured context to assist in tasks like threat hunting, network diagnostics, and anomaly detection.

Features

WireMCP exposes the following tools to MCP clients, enhancing LLM understanding of network activity:

  • `capture_packets`: Captures live traffic and returns raw packet data as JSON, enabling LLMs to analyze packet-level details (e.g., IP addresses, ports, HTTP methods).
  • `get_summary_stats`: Provides protocol hierarchy statistics, giving LLMs an overview of traffic composition (e.g., TCP vs. UDP usage).
  • `get_conversations`: Delivers TCP/UDP conversation statistics, allowing LLMs to track communication flows between endpoints.
  • `check_threats`: Captures IPs and checks them against the URLhaus blacklist, equipping LLMs with threat intelligence context for identifying malicious activity.
  • `check_ip_threats`: Performs targeted threat intelligence lookups for specific IP addresses against multiple threat feeds, providing detailed reputation and threat data.
  • `analyze_pcap`: Analyzes PCAP files to provide comprehensive packet data in JSON format, enabling detailed post-capture analysis of network traffic.
  • `extract_credentials`: Scans PCAP files for potential credentials from various protocols (HTTP Basic Auth, FTP, Telnet), aiding in security audits and forensic analysis.

How It Helps LLMs

WireMCP bridges the gap between raw network data and LLM comprehension by:

  • Contextualizing Traffic: Converts live packet captures into structured outputs (JSON, stats) that LLMs can parse and reason about.
  • Threat Detection: Integrates IOCs (currently URLhaus) to flag suspicious IPs, enhancing LLM-driven
Read from source at commit 047f5d4a8cabOBSERVED · 2026-09-29
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add wiremcp -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "wiremcp": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}
03

Exposed tools (7)

7 read · 0 write · 0 destructive.

ToolRiskDescription
analyze_pcapreadAnalyze a PCAP file and provide general packet data as JSON for LLM analysis
capture_packetsreadCapture live traffic and provide raw packet data as JSON for LLM analysis
check_ip_threatsreadCheck a given IP address against URLhaus blacklist for IOCs
check_threatsreadCapture live traffic and check IPs against URLhaus blacklist
extract_credentialsreadExtract potential credentials (HTTP Basic Auth, FTP, Telnet) from a PCAP file for LLM analysis
get_conversationsreadCapture live traffic and provide TCP/UDP conversation statistics for LLM analysis
get_summary_statsreadCapture live traffic and provide protocol hierarchy statistics for LLM analysis
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeWARN
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
declared (1 observation(s))
Network
declared (5 observation(s))
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (2)

MEDIUMFilesystem / path · fs.system_paths · CWE-22, CWE-59
index.js:26
: ['/usr/bin/tshark', '/usr/local/bin/tshark', '/opt/homebrew/bin/tshark', '/Applications/Wireshark.app/Contents/MacOS/tshark'];
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@modelcontextprotocol/sdk, axios, child_process, util, which, zod
Why it matters. 6 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass.

Audited 2026-09-29 · audit v0.4.1 · source sha 047f5d4a8cabfull audit observations/trust-audit/mcp-server/0xkoda__wire.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-09-29047f5d4a8cabSAFEB89first audit
06

Questions

What is the Wire MCP server?

An MCP for WireShark (tshark). Empower LLM's with realtime network traffic analysis capability

What tools does Wire expose?

7 in total: 7 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Wire safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Wire need?

No credential environment variables were found in its source, so it appears to need none.

How does Wire run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as wiremcp at 1.0.0.

How current is this page?

The grade is for one exact copy of the source (047f5d4a8cab), read on 2026-09-29. The repository is watched and re-audited when it changes.

Advertisement