io.github.CloudCorpRecords/pcapport
NPM · @RENETURCIOS/PCAPPORT · 2 COMPONENTS
PCAP analysis: DNS, DHCP, ICMP, TCP flows, anomalies, and SIP from capture files.
Available components
Last scanned (2 hours ago)
Scores higher than 38% of npm servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 578 tokens (~64/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@reneturcios/pcapport@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_capinfos ~45
Summarize a PCAP file: packet count, duration, size, and encapsulation.
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | Path to the packet capture file to read. |
No output schema declared.
No examples provided.
analyze_dhcp_packets ~44
Analyze DHCP packets in a PCAP file: message types, servers, and clients.
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | Path to the packet capture file to read. |
No output schema declared.
No examples provided.
analyze_dns_packets ~47
Analyze DNS packets in a PCAP file: query/response counts, top questions, and response codes.
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | Path to the packet capture file to read. |
No output schema declared.
No examples provided.
analyze_icmp_packets ~49
Analyze ICMP packets in a PCAP file: types, echo traffic, unreachable, and top talkers.
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | Path to the packet capture file to read. |
No output schema declared.
No examples provided.
analyze_sip_packets ~44
Analyze SIP packets in a PCAP file: methods, response classes, and calls.
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | Path to the packet capture file to read. |
No output schema declared.
No examples provided.
analyze_tcp_anomalies ~87
Detect TCP anomalies in a PCAP file: resets, half-open connections, no-data connections, zero window.
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | Path to the packet capture file to read. |
| server_ip | string | – | Server IP address to filter connections by. |
| server_port | integer | – | Server port to filter connections by, between 0 and 65535. |
No output schema declared.
No examples provided.
analyze_tcp_connections ~100
List TCP connections in a PCAP file with packet, byte, flag counts and state estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| detailed | boolean | – | Whether to include a per-connection summary and packet timestamps. |
| pcap_file | string | yes | Path to the packet capture file to read. |
| server_ip | string | – | Server IP address to filter connections by. |
| server_port | integer | – | Server port to filter connections by, between 0 and 65535. |
No output schema declared.
No examples provided.
analyze_tcp_retransmissions ~81
Detect TCP retransmissions in a PCAP file and compute the retransmission rate.
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | Path to the packet capture file to read. |
| server_ip | string | – | Server IP address to filter connections by. |
| threshold | number | – | Retransmission rate threshold to compare against, defaults to 0.02. |
No output schema declared.
No examples provided.
analyze_traffic_flow ~81
Analyze traffic flow to and from a server in a PCAP file.
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | Path to the packet capture file to read. |
| server_ip | string | yes | IP address of the server to analyze traffic flow for. |
| server_port | integer | – | Server port to filter traffic by, between 0 and 65535. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/pcapport MCP server?
io.github.CloudCorpRecords/pcapport runs locally as an npm package, launched with npx -y @reneturcios/pcapport. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/pcapport
claude mcp add cloudcorprecords-pcapport -- npx -y @reneturcios/pcapport
What is the io.github.CloudCorpRecords/pcapport MCP server?
io.github.CloudCorpRecords/pcapport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/pcapport. PCAP analysis: DNS, DHCP, ICMP, TCP flows, anomalies, and SIP from capture files. This page covers its npm package (@reneturcios/pcapport).
Is the io.github.CloudCorpRecords/pcapport MCP server safe to use?
io.github.CloudCorpRecords/pcapport scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.CloudCorpRecords/pcapport MCP server expose?
io.github.CloudCorpRecords/pcapport exposes 9 tools: analyze_dns_packets, analyze_dhcp_packets, analyze_icmp_packets, analyze_tcp_connections, analyze_tcp_anomalies, and 4 more. Their descriptions and schemas cost roughly 578 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/pcapport MCP server still maintained?
io.github.CloudCorpRecords/pcapport is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/pcapport MCP server under?
io.github.CloudCorpRecords/pcapport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.