F
licenseB
qualityD
maintenanceA lightweight MCP server built on mitmproxy that lets LLMs capture, inspect, replay, and modify HTTP traffic through a set of focused tools.
13
7
-
mitmproxy-mcp
by snapspecter
Related Servers
Alternatives to mitmproxy-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables Claude Code to inspect, modify, and block HTTP traffic via mitmproxy, with tools for flow capture, filtering, and rule creation.1-
- AlicenseAqualityCmaintenanceEnables AI agents to interact with Charles Proxy for HTTP traffic analysis, supporting incremental harvest, checkpoint timelines, and rich filtering tools.138MIT
- AlicenseBqualityCmaintenanceEnables AI agents to connect to Charles Proxy for live and historical traffic analysis, summary-first insights, request detail inspection, and data-driven mock creation via Map Local/Remote.47MIT
- FlicenseAqualityAmaintenanceRuns a local HTTPS MITM proxy to intercept and mock network traffic from Android devices at the network level, enabling AI agents to register JSON transform rules and static responses without modifying app source code.215 npm-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with websites by capturing browser traffic and exposing them as named MCP tools, requiring no public API.Apache 2.0
TDQS
C2/5.0
Scored across 25 tools
Disambiguation2/5
Many tools have empty descriptions (e.g., add_interception_rule, clear_rules, detect_auth_pattern) or similar purposes (extract_from_flow vs extract_session_variable, set_global_header vs remove_global_header), making it hard to distinguish their roles. The overlap and lack of clarity cause confusion.
Naming Consistency2/5
Naming is inconsistent: some use verb_noun snake_case (add_interception_rule, clear_traffic), others use get_* (get_api_patterns, get_flow_schema), and some are imperative (start_proxy, stop_proxy). The mix of patterns and missing descriptions for several tools reduces predictability.
Tool Count3/5
25 tools is on the high side for a proxy/interception tool. While the domain can support many utilities, several tools seem redundant or have empty descriptions, making the count feel inflated without clear value.
Completeness2/5
The tool set covers capture, replay, and rule management but lacks essential features like interactive rule modification, live traffic modification, and individual rule removal. Security testing is partial (only fuzz_endpoint). Gaps in rule lifecycle and real-time interception are notable.
Maintenance
ActivityInactive
ResponsivenessSlow