Skip to main content
Glama

Related Servers

Alternatives to proxy-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      An 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.
      11
      240
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP 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.
      35
      6 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an LLM agent to capture a single Windows process's network traffic by process name — listing monitorable apps, starting and stopping L3/L4 or L7 captures, and exporting the results as pcap, JSON, and plaintext HTTP logs. The server can also drive an optional mitmproxy layer to decrypt HTTP(S) for the target process only.
      MIT

    TDQS

    B3.4/5.0

    Scored across 72 tools

    Disambiguation4/5

    Tools are mostly grouped by clear domains (proxy, session, interceptor, humanizer, fingerprinting), and descriptions clarify near-neighbor cases like traffic search vs session body search. However, some pairs could still be confused, such as proxy_get_exchange vs proxy_get_session_exchange vs interceptor_browser_get_network_field, and the convenience rule creators overlap conceptually with proxy_add_rule.

    Naming Consistency4/5

    The naming follows a strong snake_case verb_noun pattern with consistent prefixes like proxy_, interceptor_browser_, and humanizer_. Minor inconsistencies exist: clear vs remove for upstreams, the deprecated proxy_set_ja3_spoof alongside proxy_set_fingerprint_spoof, and proxy_enable_server_tls_capture described as a toggle despite its name.

    Tool Count2/5

    72 tools is a very large surface for an MCP server, even for a broad proxy/interception platform. Many tools are highly specialized and could be consolidated, such as convenience rule wrappers, session query variants, and the deprecated JA3 tool.

    Completeness5/5

    The toolset covers the full proxy lifecycle: start/stop/status, CA management, upstream configuration, rules, traffic capture and search, sessions, HAR import/export, TLS fingerprinting, browser automation, humanization, and process/Docker interception. There are no major workflow dead ends; list-style tools fill gaps where dedicated getters are absent.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive