Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
PCAP analysis: DNS, DHCP, ICMP, TCP flows, anomalies, and SIP from capture files.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"pcapport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/pcapport",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add pcapport -- npx -y @reneturcios/pcapport mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"pcapport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/pcapport",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"pcapport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/pcapport",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Apify MCP Server
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
npx @reneturcios/pcapport analyze_capinfos '{"pcap_file":"capture.pcap"}'
Or run the container image:
docker run -i ghcr.io/cloudcorprecords/pcapport
The container defaults to the MCP server. Pass CLI arguments to use it as a CLI instead.
The CLI mirrors the tools: one subcommand per tool, taking its arguments as a single JSON object.
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.
One bin serves both faces. The mcp subcommand starts a stdio MCP server:
npx -y @reneturcios/pcapport mcp
MCP client configuration:
{
"mcpServers": { "pcapport": { "command": "npx", "args": ["-y", "@reneturcios/pcapport", "mcp"] } } }
| Tool | Input | What it does |
|---|---|---|
analyze_dns_packets | pcap_file (required) | DNS query/response counts, top questions (aggregated, top 20), and a response-code summary. |
analyze_dhcp_packets | pcap_file (required) | DHCP packet count by message type (discover, offer, request, ack, ...), server IPs, and client MACs. |
analyze_icmp_packets | pcap_file (required) | ICMP counts by type, echo requests/replies, unreachable count, and top talkers. |
analyze_tcp_connections | pcap_file (required), server_ip, server_port, detailed | Connections 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_anomalies | pcap_file (required), server_ip, server_port | Counts 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_retransmissions | pcap_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_flow | pcap_file (required), server_ip (required), server_port | Packets and bytes to and from the server, the unique client count, and the top clients by bytes. |
analyze_sip_packets | pcap_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_capinfos | pcap_file (required) | Packet count, duration, data bytes, average packet size, first/last packet times, encapsulation, and capture length. |
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.
npm install
npm run build # tsc -> dist/ npm test # node test runner over test/*.test.ts, synthetic captures only, no network npm run dev # run the CLI from source via tsx
MIT — see LICENSE.