This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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/pcapportThe container defaults to the MCP server. Pass CLI arguments to use it as a CLI instead.
Related MCP server: PacketMaster
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 --versionExit 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 mcpMCP client configuration:
{
"mcpServers": {
"pcapport": {
"command": "npx",
"args": ["-y", "@reneturcios/pcapport", "mcp"]
}
}
}Tool | Input | What it does |
|
| DNS query/response counts, top questions (aggregated, top 20), and a response-code summary. |
|
| DHCP packet count by message type (discover, offer, request, ack, ...), server IPs, and client MACs. |
|
| ICMP counts by type, echo requests/replies, unreachable count, and top talkers. |
|
| 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 |
|
| 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. |
|
| 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. |
|
| Packets and bytes to and from the server, the unique client count, and the top clients by bytes. |
|
| 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 |
|
| 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 tsxMIT — see LICENSE.
This server cannot be deployed
Capture, inspect & debug HTTPS traffic across iOS, Android, browsers & backends — 304 MCP tools.
238+ dev tools via MCP: JSON, QR, PDF, DNS, hash, UUID, code review, JWT, SSL, WHOIS, and more
DBRE-grade SQL analysis inside any MCP client. No connection. No install. Paste a query.
2,000+ MCP servers read at source level. Know what one does before you connect. Free, no key.
