mitmproxy-mcp
Related Servers
Alternatives to mitmproxy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI agents to intercept, inspect, and modify HTTP traffic, with tools for searching, filtering, and managing captured requests and interceptors.25 npm8MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for mitmproxy that lets any MCP client analyze, intercept, and replay HTTP/HTTPS traffic.9MIT
- AlicenseAqualityFmaintenanceAn MCP server that enables AI assistants to control HTTP Toolkit for intercepting, inspecting, and debugging HTTP(S) traffic from browsers, mobile devices, and Docker containers. It provides tools for server management, interceptor activation, and sending HTTP requests through natural language commands.2319 npm1MIT
- FlicenseAqualityAmaintenanceAn MCP server that bridges LLMs with dynamic real-world data by leveraging Chrome DevTools Protocol to intercept and reconstruct network traffic, enabling AI agents to extract high-quality structured data from complex web environments.389-
- AlicenseAqualityCmaintenanceA lightweight MCP server that enables LLMs to interact with any REST API via HTTP requests, with smart response truncation, TypeScript type generation, and field extraction.520 npm1MIT
- AlicenseAqualityFmaintenanceAn MCP server that enables AI assistants to capture and analyze HTTP/HTTPS traffic from Android devices. It supports smart searching of network requests and provides tools for detailed traffic analysis via natural language.11232MIT
TDQS
Scored across 13 tools
Each tool targets a distinct operation: proxy lifecycle management, flow singular vs plural actions, and request sending. Descriptions clearly differentiate between creating a flow without sending versus sending a request.
All tool names follow a consistent prefix_verb pattern with underscores (e.g., proxy_start, flows_list, flow_update). Singular vs plural prefixes are used appropriately for single vs batch operations.
13 tools cover proxy management, flow CRUD, load/save, replay, and request sending without unnecessary overlap. The scope aligns well with the mitmproxy domain.
The set covers the full lifecycle: proxy start/stop/status, flow capture, retrieval, creation, modification, deletion, persistence, and replay/send. No obvious gaps for standard proxy operations.