A modular Python MCP (Model Context Protocol) Server for analyzing PCAP files. mcpcap enables LLMs to read and analyze network packet captures with protocol-specific analysis tools that accept local file paths or remote URLs as parameters (no file uploads - provide the path or URL to your PCAP file).
mcpcap uses a modular architecture to analyze different network protocols found in PCAP files. Each module provides specialized analysis tools that can be called independently with any PCAP file, making it perfect for integration with Claude Desktop and other MCP clients.
- Stateless MCP Tools: Each analysis accepts PCAP file paths or URLs as parameters (no file uploads)
- Modular Architecture: DNS, DHCP, ICMP, and CapInfos modules with easy extensibility for new protocols
- Local & Remote PCAP Support: Analyze files from local storage or HTTP URLs
- Scapy Integration: Leverages scapy's comprehensive packet parsing capabilities
- Specialized Analysis Prompts: Security, networking, and forensic analysis guidance
- JSON Responses: Structured data format optimized for LLM consumption
mcpcap requires Python 3.10 or greater.
pip install mcpcap
uv add mcpcap
uvx mcpcap
Start mcpcap as a stateless MCP server:
# Default: Start with DNS, DHCP, and ICMP modules
mcpcap
# Start with specific modules only
mcpcap --modules dns
# With packet analysis limits
mcpcap --max-packets 1000
Configure your MCP client (like Claude Desktop) to connect to the mcpcap server:
{
"mcpServers": {
"mcpcap": {
"command": "mcpcap",
"args": []
}
}
}
Use the analysis tools with any PCAP file by providing the file path or URL (not file uploads):
DNS Analysis:
analyze_dns_packets("/path/to/dns.pcap")
analyze_dns_packets("https://example.com/remote.pcap")
DHCP Analysis:
analyze_dhcp_packets("/path/to/dhcp.pcap")
analyze_dhcp_packets("https://example.com/dhcp-capture.pcap")
ICMP Analysis:
analyze_icmp_packets("/path/to/icmp.pcap")
analyze_icmp_packets("https://example.com/ping-capture.pcap")
CapInfos Analysis:
analyze_capinfos("/path/to/any.pcap")
analyze_capinfos("https://example.com/capture.pcap")
analyze_dns_packets(pcap_file)
: Complete DNS traffic analysis- Extract DNS queries and responses
- Identify queried domains and subdomains
- Analyze query types (A, AAAA, MX, CNAME, etc.)
- Track query frequency and patterns
- Detect potential security issues
analyze_dhcp_packets(pcap_file)
: Complete DHCP traffic analysis- Track DHCP transactions (DISCOVER, OFFER, REQUEST, ACK)
- Identify DHCP clients and servers
- Monitor IP address assignments and lease information
- Analyze DHCP options and configurations
- Detect DHCP anomalies and security issues
analyze_icmp_packets(pcap_file)
: Complete ICMP traffic analysis- Analyze ping requests and replies with response times
- Identify network connectivity and reachability issues
- Track TTL values and routing paths (traceroute data)
- Detect ICMP error messages (unreachable, time exceeded)
- Monitor for potential ICMP-based attacks or reconnaissance
analyze_capinfos(pcap_file)
: PCAP file metadata and statistics- File information (size, name, link layer encapsulation)
- Packet statistics (count, data size, average packet size)
- Temporal analysis (duration, timestamps, packet rates)
- Data throughput metrics (bytes/second, bits/second)
- Similar to Wireshark's capinfos(1) utility
mcpcap provides specialized analysis prompts to guide LLM analysis:
security_analysis
- Focus on threat detection, DGA domains, DNS tunnelingnetwork_troubleshooting
- Identify DNS performance and configuration issuesforensic_investigation
- Timeline reconstruction and evidence collection
dhcp_network_analysis
- Network administration and IP managementdhcp_security_analysis
- Security threats and rogue DHCP detectiondhcp_forensic_investigation
- Forensic analysis of DHCP transactions
icmp_network_diagnostics
- Network connectivity and path analysisicmp_security_analysis
- ICMP-based attacks and reconnaissance detectionicmp_forensic_investigation
- Timeline reconstruction and network mapping
# Load specific modules
mcpcap --modules dns # DNS analysis only
mcpcap --modules dhcp # DHCP analysis only
mcpcap --modules icmp # ICMP analysis only
mcpcap --modules dns,dhcp,icmp,capinfos # All modules (default)
# Limit packet analysis for large files
mcpcap --max-packets 1000
mcpcap --modules dns,dhcp,icmp,capinfos --max-packets 500
mcpcap [--modules MODULES] [--max-packets N]
Options:
--modules MODULES
: Comma-separated modules to load (default:dns,dhcp,icmp,capinfos
)- Available modules:
dns
,dhcp
,icmp
,capinfos
- Available modules:
--max-packets N
: Maximum packets to analyze per file (default: unlimited)
Examples:
# Start with all modules
mcpcap
# DNS analysis only
mcpcap --modules dns
# With packet limits for large files
mcpcap --max-packets 1000
Example PCAP files are included in the examples/
directory:
dns.pcap
- DNS traffic for testing DNS analysisdhcp.pcap
- DHCP 4-way handshake captureicmp.pcap
- ICMP ping and traceroute traffic
npm install -g @modelcontextprotocol/inspector
npx @modelcontextprotocol/inspector mcpcap
Then test the tools:
// In the MCP Inspector web interface
analyze_dns_packets("./examples/dns.pcap")
analyze_dhcp_packets("./examples/dhcp.pcap")
analyze_icmp_packets("./examples/icmp.pcap")
analyze_capinfos("./examples/dns.pcap")
mcpcap's modular design supports easy extension:
- BaseModule: Shared file handling, validation, and remote download
- Protocol Modules: DNS, DHCP, and ICMP analysis implementations
- MCP Interface: Tool registration and prompt management
- FastMCP Framework: MCP server implementation
MCP Client Request → analyze_*_packets(pcap_file)
→ BaseModule.analyze_packets()
→ Module._analyze_protocol_file()
→ Structured JSON Response
Create new protocol modules by:
- Inheriting from
BaseModule
- Implementing
_analyze_protocol_file(pcap_file)
- Registering analysis tools with the MCP server
- Adding specialized analysis prompts
Future modules might include:
- HTTP/HTTPS traffic analysis
- TCP connection tracking
- BGP routing analysis
- SSL/TLS certificate analysis
- Network forensics tools
Both analysis tools accept remote PCAP files via HTTP/HTTPS URLs:
# Examples of remote analysis
analyze_dns_packets("https://wiki.wireshark.org/uploads/dns.cap")
analyze_dhcp_packets("https://example.com/network-capture.pcap")
analyze_icmp_packets("https://example.com/ping-test.pcap")
analyze_capinfos("https://example.com/network-metadata.pcap")
Features:
- Automatic temporary download and cleanup
- Support for
.pcap
,.pcapng
, and.cap
files - HTTP/HTTPS protocols supported
When analyzing PCAP files:
- Files may contain sensitive network information
- Remote downloads are performed over HTTPS when possible
- Temporary files are cleaned up automatically
- Consider the source and trustworthiness of remote files
Contributions welcome! Areas for contribution:
- New Protocol Modules: Add support for HTTP, BGP, TCP, etc.
- Enhanced Analysis: Improve existing DNS/DHCP analysis
- Security Features: Add more threat detection capabilities
- Performance: Optimize analysis for large PCAP files
MIT
- Python 3.10+
- scapy (packet parsing and analysis)
- requests (remote file access)
- fastmcp (MCP server framework)
- GitHub: github.com/mcpcap/mcpcap
- Documentation: docs.mcpcap.ai
- Website: mcpcap.ai
For questions, issues, or feature requests, please open an issue on GitHub.