Skip to main content
Glama

Related Servers

Alternatives to mitmAny

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
      245
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI agents to intercept, inspect, and modify HTTP traffic, with tools for searching, filtering, and managing captured requests and interceptors.
      8
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      HTTP(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.
      20
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: observation lifecycle (begin/end/mark), metadata access (get_flow), body access (read_body), and status (capture_status). The one soft overlap is summarize_traffic versus search_flows, since both filter on observation_id, host, path, method, and status; the descriptions differentiate them (aggregated counts versus newest-first ID listing with cursors), but an agent could still pick the wrong one for a quick lookup.

    Naming Consistency4/5

    Eight of nine names follow a consistent snake_case verb_noun pattern (begin_observation, end_observation, get_flow, read_body, search_flows, wait_for_flows, summarize_traffic, mark_observation). capture_status is the lone noun-only outlier, a minor deviation that stays readable.

    Tool Count5/5

    Nine tools is well within the ideal 3-15 range and each earns its place: two observation boundary operations, one annotation, one status read, and five flow inspection/streaming operations. Nothing feels redundant or padded.

    Completeness4/5

    The surface covers the core lifecycle: create/end/mark observations, search and summarize flows, read metadata and bounded bodies, and wait for new traffic. The main gap is the absence of a list_observations operation, so an agent that loses an observation_id has no way to rediscover bookmarks; capture start/stop and traffic clearing appear intentionally out of scope but are noted as external.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues