ai.mcpcap/mcpcap
PYPI · MCPCAP
An MCP server for analyzing PCAP files.
Available components
Last scanned (10 hours ago)
Scores higher than 80% of PyPI servers
Category Security
Recent critical change
CVE-2026-32871 affects this package (23 Sept 2026). See the changelog before you install this server.
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 Security90
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects fastmcp 3.2.4, a direct dependency. A fixed version is available. View diagnostics → Fail
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 3 of 60 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mcpcap/mcpcap). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 35 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1060 tokens (~117/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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.
- 5 Nov 26 −14
- Stability: pass → unverified ▼ security
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 +14
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 −3
- GHSA-7xgj-8392-5q4r affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
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 pypi/mcpcap@0.10.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mcpcap/mcpcap |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mcpcap/mcpcap/.github/workflows/release.yml@refs/tags/v0.10.0 |
| Rekor log index | 3009688114 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:077232924256edb5936cb43789e7bb6d4d5778dc6ac06ac78fd11a97912bd4ad |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-7xgj-8392-5q4r | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 60 packages
| Packages resolved | 60 |
|---|---|
| Stale | 2 |
| No linked repository | 1 |
| 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 ~119
Return metadata from a PCAP file, similar to Wireshark's capinfos utility. IMPORTANT: This tool expects a FILE PATH or URL, not file content. - For local files: "/path/to/capture.pcap" - For remote files: "https://example.com/capture.pcap" - File uploads are NOT supported - save the file locally first
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | Path to local PCAP file or HTTP URL to remote PCAP file (NOT file content - must be a path or URL) |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_dhcp_packets ~131
Analyze DHCP packets from a PCAP file and return comprehensive analysis results. FILE UPLOAD LIMITATION: This MCP tool cannot process files uploaded through Claude's web interface. Files must be accessible via URL or local file path. SUPPORTED INPUT FORMATS: - Remote files: "https://example.com/capture.pcap" - Local files: "/absolute/path/to/capture.pcap" UNSUPPORTED: - Files uploaded through Claude's file upload feature - Base64 file content - Relative file paths
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | HTTP URL or absolute local file path to PCAP file |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_dns_packets ~130
Analyze DNS packets from a PCAP file and return comprehensive analysis results. FILE UPLOAD LIMITATION: This MCP tool cannot process files uploaded through Claude's web interface. Files must be accessible via URL or local file path. SUPPORTED INPUT FORMATS: - Remote files: "https://example.com/capture.pcap" - Local files: "/absolute/path/to/capture.pcap" UNSUPPORTED: - Files uploaded through Claude's file upload feature - Base64 file content - Relative file paths
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | HTTP URL or absolute local file path to PCAP file |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_icmp_packets ~132
Analyze ICMP packets from a PCAP file and return comprehensive analysis results. FILE UPLOAD LIMITATION: This MCP tool cannot process files uploaded through Claude's web interface. Files must be accessible via URL or local file path. SUPPORTED INPUT FORMATS: - Remote files: "https://example.com/capture.pcap" - Local files: "/absolute/path/to/capture.pcap" UNSUPPORTED: - Files uploaded through Claude's file upload feature - Base64 file content - Relative file paths
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | HTTP URL or absolute local file path to PCAP file |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_sip_packets ~131
Analyze SIP packets from a PCAP file and return structured signaling details. FILE UPLOAD LIMITATION: This MCP tool cannot process files uploaded through Claude's web interface. Files must be accessible via URL or local file path. SUPPORTED INPUT FORMATS: - Remote files: "https://example.com/capture.pcap" - Local files: "/absolute/path/to/capture.pcap" UNSUPPORTED: - Files uploaded through Claude's file upload feature - Base64 file content - Relative file paths
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | HTTP URL or absolute local file path to PCAP file |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_tcp_anomalies ~95
Detect TCP traffic patterns through statistical analysis. This tool analyzes TCP traffic to identify observable patterns without making assumptions about root causes. It provides factual metrics and pattern detection that can be used for further investigation.
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | HTTP URL or absolute local file path to PCAP file |
| server_ip | – | – | Optional filter for server IP address |
| server_port | – | – | Optional filter for server port |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_tcp_connections ~178
Analyze TCP connection states and lifecycle. This is the core tool for TCP connection analysis, solving 80% of TCP-related issues. FILE UPLOAD LIMITATION: This MCP tool cannot process files uploaded through Claude's web interface. Files must be accessible via URL or local file path. SUPPORTED INPUT FORMATS: - Remote files: "https://example.com/capture.pcap" - Local files: "/absolute/path/to/capture.pcap" UNSUPPORTED: - Files uploaded through Claude's file upload feature - Base64 file content - Relative file paths
| Name | Type | Req | Description |
|---|---|---|---|
| detailed | boolean | – | Whether to return detailed connection information |
| pcap_file | string | yes | HTTP URL or absolute local file path to PCAP file |
| server_ip | – | – | Optional filter for server IP address |
| server_port | – | – | Optional filter for server port |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_tcp_retransmissions ~66
Analyze TCP retransmission patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | HTTP URL or absolute local file path to PCAP file |
| server_ip | – | – | Optional filter for server IP address |
| threshold | number | – | Retransmission rate threshold (default: 2%) |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_traffic_flow ~78
Analyze bidirectional traffic flow characteristics. Identifies traffic direction, asymmetry, RST sources, and data transfer patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| pcap_file | string | yes | HTTP URL or absolute local file path to PCAP file |
| server_ip | string | yes | Server IP address (required) |
| server_port | – | – | Optional filter for server port |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the ai.mcpcap/mcpcap MCP server?
ai.mcpcap/mcpcap runs locally as a PyPI package, launched with uvx mcpcap. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcpcap
claude mcp add ai-mcpcap-mcpcap -- uvx mcpcap
What is the ai.mcpcap/mcpcap MCP server?
ai.mcpcap/mcpcap is an MCP server listed in the public MCP registry as ai.mcpcap/mcpcap. An MCP server for analyzing PCAP files. This page covers its PyPI package (mcpcap).
Is the ai.mcpcap/mcpcap MCP server safe to use?
ai.mcpcap/mcpcap scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. Its build provenance is signed and verified. 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 ai.mcpcap/mcpcap MCP server expose?
ai.mcpcap/mcpcap exposes 9 tools: analyze_dns_packets, analyze_dhcp_packets, analyze_icmp_packets, analyze_capinfos, analyze_tcp_connections, and 4 more. Their descriptions and schemas cost roughly 1,060 tokens of context every time the server is loaded.
Is the ai.mcpcap/mcpcap MCP server still maintained?
ai.mcpcap/mcpcap 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 ai.mcpcap/mcpcap MCP server under?
ai.mcpcap/mcpcap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.