A
licenseC
qualityA
maintenanceTransforms mitmproxy into a toolset for AI agents to inspect, modify, and replay HTTP/HTTPS traffic in real-time.
25
267 PyPI
133
MIT
mcp-security-mitmproxy
by dandgabr
Related Servers
Alternatives to mcp-security-mitmproxy
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-
- AlicenseAqualityAmaintenanceHTTP(S) and WebSocket debugging proxy, like Proxyman or Charles, that AI agents drive over MCP: summarize captured traffic, read requests with secrets masked, diff a working request against a failing one, mock responses, set breakpoints and throttle the network.201MIT
- FlicenseBqualityDmaintenanceA lightweight MCP server built on mitmproxy that lets LLMs capture, inspect, replay, and modify HTTP traffic through a set of focused tools.138-
- AlicenseAqualityDmaintenanceGives AI agents a browser that bypasses bot detection, a MITM proxy for traffic interception, and a Python sandbox to autonomously write and execute security exploits.393MIT
- AlicenseAqualityCmaintenanceEnables AI agents to interact with Charles Proxy for HTTP traffic analysis, supporting incremental harvest, checkpoint timelines, and rich filtering tools.138MIT
TDQS
B3.2/5.0
Scored across 18 tools
Disambiguation5/5
Every tool targets a distinct mitmproxy operation: session lifecycle, flow inspection/export/filtering, and rule management are cleanly separated. Even similarly named start/stop tools are disambiguated by mitmdump vs mitmweb mode, and the rule tools map clearly to remote/local/header/body mutations.
Naming Consistency4/5
Most tools follow a verb_noun pattern under a mitm/mitmdump/mitmweb prefix, e.g. get_flows, export_flow, clear_rules. The noun-first session_list and session_status tools deviate slightly, and get vs list is mixed across tools, but the overall pattern remains predictable.
Tool Count3/5
At 18 tools, this is above the ideal 3–15 range and feels heavy, though the tools are not redundant. The count is justified by the breadth of mitmproxy functionality but still pushes the server into the 'heavy' band.
Completeness4/5
The server covers the complete proxy workflow: start/stop sessions, replay, retrieve/filter/export flows, and apply map/modify rules. Minor gaps remain, such as no direct intercept/breakpoint controls or explicit session/dump cleanup, but agents can work around these with the provided command and rule tools.
Maintenance
ActivitySlowing
ResponsivenessNo issues