Skip to main content
Glama
ElonJask

Reqable MCP Server

by ElonJask
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Reqable MCP Server

No user-submitted related servers found.

    Related Servers

    • reqable-mcp

      Wanghaibo10
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that brings Reqable's captured HTTP traffic into Claude Code conversations, enabling querying, searching, waiting for, and analyzing requests without requiring Reqable Pro.
      7
      MIT

    • ProxyPin MCP Server

      ElonJask
      A
      license
      B
      quality
      D
      maintenance
      Exposes ProxyPin's local network capture history to MCP-capable clients for searching, analyzing, and detailing captured HTTP traffic. It enables users to perform API structure analysis and generate client-side code directly from captured requests.
      6
      17
      MIT

    • Reqable Capture Reader MCP

      iambond50-svg
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query, filter, and analyze local HTTP capture records and REST API test data from the Reqable tool. It provides read-only access to inspect request/response details, headers, and statistics through natural language.
      26
      -

    • whistle.agent-mcp

      wilsonyiyi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible AI assistants to directly search and inspect Whistle-captured HTTP, HTTPS, and WebSocket traffic, including full session details, timing, and frame analysis, without modifying Whistle configuration.
      9 npm
      MIT

    • Android Proxy MCP

      zhizhuodemao
      A
      license
      A
      quality
      F
      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
      233
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources like HTTP requests, WebSocket sessions, or data operations, with clear boundaries. However, some overlap exists between list_websocket_sessions and list_active_websocket_sessions, which could cause confusion in selection without careful reading of descriptions.

    Naming Consistency5/5

    Tool names follow a highly consistent snake_case pattern with clear verb_noun structures throughout, such as analyze_api, get_request, list_requests, and search_websocket_messages. There are no deviations in naming conventions, making the set predictable and readable.

    Tool Count4/5

    With 17 tools, the count is slightly high but reasonable for the server's scope in API and WebSocket analysis, covering ingestion, querying, and data management. It feels comprehensive without being overly bloated, though it borders on the heavy side for typical MCP servers.

    Completeness5/5

    The tool set provides complete coverage for the domain of API and WebSocket analysis, including ingestion (import_har, ingest_status), querying (list_requests, search_requests), detailed access (get_request, get_websocket_session), analysis (analyze_api, analyze_websocket_session), and data management (export, repair, tail). No obvious gaps are present, supporting full lifecycle workflows.

    Maintenance

    ActivityInactive
    ResponsivenessSlow

    Resources