Skip to main content
Glama

Related Servers

Alternatives to whistle-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI to manage whistle mock rules, values, and inspect network sessions, facilitating API mocking and debugging through natural language.
      17
      6 npm
      1
      MIT
    • 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
    • A
      license
      A
      quality
      F
      maintenance
      An 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.
      23
      20 npm
      1
      MIT
    • 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

    TDQS

    C2.8/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources (rules, values, groups) and actions (create, delete, rename, enable/disable), but some overlap exists: 'getAllValues' and 'getRules' both retrieve data, and 'toggle' tools for various interception settings could be confused. Descriptions help clarify, but minor ambiguity remains.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, using camelCase uniformly (e.g., createRule, deleteGroup, toggleProxy). There are no deviations in naming conventions, making the set predictable and readable.

    Tool Count3/5

    With 32 tools, the count is borderline high for a whistle proxy management server. While it covers many operations, it feels heavy and could potentially be streamlined, as some tools (e.g., multiple toggle functions) might be consolidated without losing functionality.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for managing rules, values, and groups, including create, read, update, delete, enable/disable, and renaming. It also covers server status, interception controls, and request replay, leaving no obvious gaps for the whistle proxy domain.

    Maintenance

    ActivityInactive
    ResponsivenessWithin a week