Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
PCAP analysis: DNS, DHCP, ICMP, TCP flows, anomalies, and SIP from capture files.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"pcapport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/pcapport",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add pcapport -- npx -y @reneturcios/pcapport mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pcapport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/pcapport",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"pcapport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/pcapport",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, topo^alpin
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.