A
licenseNot graded
qualityB
maintenanceAn MCP server that enables AI agents to intercept, inspect, and modify HTTP traffic, with tools for searching, filtering, and managing captured requests and interceptors.
14
8
MIT
Android Proxy MCP
by zhizhuodemao
Related Servers
Alternatives to Android Proxy MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server for parsing and analyzing HAR files, enabling AI assistants to inspect network traffic with automatic redaction of sensitive authentication headers.7MIT
- 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.23171MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that leverages Wireshark/Tshark for real-time and offline network traffic analysis, enabling AI assistants to capture, parse, and detect threats with automated scanning and threat intelligence.2MIT
- AlicenseAqualityDmaintenanceMCP server for intercepting and mocking HTTP(S) traffic via a Mockttp proxy, with tools for Android emulator setup, traffic inspection, protobuf analysis, and rule-based manipulation.3517MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to drive real Android apps, capture API traffic, and test mobile-native attack surfaces, similar to Playwright for mobile.MIT
TDQS
A3.7/5.0
Scored across 11 tools
Disambiguation5/5
Each tool has a distinct purpose with clear boundaries: device management (list, get, clear/set proxy), certificate handling (get_cert_info), proxy server control (proxy_status), and traffic analysis (clear, list, get_detail, read_body, search). The descriptions explicitly differentiate overlapping tools like traffic_get_detail (metadata only) vs traffic_read_body (body content), preventing misselection.
Naming Consistency5/5
Tool names follow a consistent snake_case pattern with clear prefixes: 'android_' for device operations, 'get_'/'traffic_' for certificate and traffic functions, and descriptive verb_noun combinations (e.g., traffic_list, traffic_search). No mixing of conventions or vague names, making the set predictable and readable.
Tool Count5/5
11 tools are well-scoped for the server's purpose of Android proxy management and traffic analysis. The count covers device handling, proxy setup, certificate guidance, and comprehensive traffic inspection (listing, filtering, searching, reading details/bodies), with each tool earning its place without bloat or gaps.
Completeness5/5
The toolset provides complete coverage for the Android proxy domain: device discovery and info, proxy configuration (clear/set), certificate setup guidance, proxy server status, and full traffic lifecycle (capture via proxy, list, filter, search, view metadata, read bodies, clear). No obvious gaps exist; agents can perform end-to-end workflows without dead ends.
Maintenance
ActivityInactive
ResponsivenessUnresponsive