Pcapport

io.github.CloudCorpRecords由 GitHub 账号 CloudCorpRecords 发布v0.1.0更新于 Nov 3, 2026

PCAP分析：从捕获文件中分析DNS、DHCP、ICMP、TCP流、异常和SIP。

AI 翻译由 AI 模型根据下方的原文描述翻译，可能有误。

原文描述

PCAP analysis: DNS, DHCP, ICMP, TCP flows, anomalies, and SIP from capture files.

已验证STDIO仅桌面

概览

Pcapport 的本地 MCP 服务；无需登录；STDIO。

暂无 AI 概览：以下信息来自注册中心条目和服务本身。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Pcapport，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

pcapport

pcapport analyses PCAP capture files entirely on your own machine. Point it at a classic libpcap file and it summarises what is inside: DNS questions and response codes, DHCP message types and the servers and clients involved, ICMP traffic, TCP connections with state estimates, TCP anomalies and retransmissions, traffic flow to and from one server, SIP calls, and basic capture information such as packet count, duration, and encapsulation.

There is no network access, no API key, and no live capture: the tool only reads the capture file you name. The parser is an original minimal implementation covering Ethernet (including a single VLAN tag) and raw-IP captures carrying IPv4, with TCP, UDP, and ICMP decoded, and DNS, DHCP, and SIP payloads understood.

Install

bash
npx @reneturcios/pcapport analyze_capinfos '{"pcap_file":"capture.pcap"}'

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/pcapport

The container defaults to the MCP server. Pass CLI arguments to use it as a CLI instead.

CLI

The CLI mirrors the tools: one subcommand per tool, taking its arguments as a single JSON object.

bash
pcapport analyze_capinfos '{"pcap_file":"capture.pcap"}'pcapport analyze_dns_packets '{"pcap_file":"capture.pcap"}'pcapport analyze_tcp_connections '{"pcap_file":"capture.pcap","detailed":true}'pcapport analyze_tcp_retransmissions '{"pcap_file":"capture.pcap","threshold":0.05}'pcapport analyze_traffic_flow '{"pcap_file":"capture.pcap","server_ip":"10.0.0.5","server_port":80}'pcapport --version

Exit codes: 0 on success, 1 on an error (the error names the problem, e.g. a bad PCAP magic or a truncated file), 2 for usage errors. An empty capture is not an error: tools return zeroed summaries for it.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/pcapport mcp

MCP client configuration:

json
{  "mcpServers": {    "pcapport": {      "command": "npx",      "args": ["-y", "@reneturcios/pcapport", "mcp"]    }  }}

Tools

ToolInputWhat it does
analyze_dns_packetspcap_file (required)DNS query/response counts, top questions (aggregated, top 20), and a response-code summary.
analyze_dhcp_packetspcap_file (required)DHCP packet count by message type (discover, offer, request, ack, ...), server IPs, and client MACs.
analyze_icmp_packetspcap_file (required)ICMP counts by type, echo requests/replies, unreachable count, and top talkers.
analyze_tcp_connectionspcap_file (required), server_ip, server_port, detailedConnections keyed by the normalised 4-tuple with client/server, packets, bytes, SYN/FIN/RST counts, and a state estimate (established, closed, reset, half-open). With detailed, a per-connection timestamp summary is included.
analyze_tcp_anomaliespcap_file (required), server_ip, server_portCounts of reset connections, half-open connections (SYN with no SYN-ACK), connections without data, and zero-window advertisements, computed from flags and window fields.
analyze_tcp_retransmissionspcap_file (required), server_ip, threshold (default 0.02)A retransmission is a repeated (tuple, sequence, payload-length) data segment. Reports data segments, retransmissions, the rate, whether it exceeds the threshold, and the top offending connections.
analyze_traffic_flowpcap_file (required), server_ip (required), server_portPackets and bytes to and from the server, the unique client count, and the top clients by bytes.
analyze_sip_packetspcap_file (required)SIP requests by method, responses by status class, and calls (Call-ID, From, To). Payloads on port 5060 plus any payload starting with a SIP method or SIP/2.0 are considered.
analyze_capinfospcap_file (required)Packet count, duration, data bytes, average packet size, first/last packet times, encapsulation, and capture length.

Scope and limits

The parser covers classic libpcap only (big/little endian, micro- and nanosecond timestamps) — no pcapng. Only IPv4 is decoded; IPv6 and other ethertypes are counted in packet totals but not analysed. There is no TCP stream reassembly, so SIP over TCP is matched per segment, and TLS payloads are opaque. Anomaly and state heuristics are deliberately simple approximations, not a substitute for a full tshark-grade analysis.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, synthetic captures only, no networknpm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

来源：README.md，提交 788aeab

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

1
  1. v0.1.0最新Nov 3, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分