Skip to main content
Glama
fdciabdul

httptoolkit-mcp

by fdciabdul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to httptoolkit-mcp

No user-submitted related servers found.

    Related Servers

    • httap

      mtford90
      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.
      17 npm
      8
      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

    • mockserver-mcp

      Akkshay10
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for interacting with MockServer, enabling AI assistants to create mock HTTP expectations, verify requests, clear state, and manage MockServer instances programmatically.
      6
      43 npm
      1
      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

    A3.7/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools have distinct purposes, such as intercepting different targets (Chrome, Docker, Android) or managing interceptors. However, some overlap exists: 'activate_interceptor' is a generic version that could be confused with specific intercept tools like 'intercept_chrome', though descriptions clarify this. The dedicated tools are well-differentiated by target type.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as 'activate_interceptor', 'capture_traffic', 'deactivate_interceptor', and 'list_interceptors'. All tools use snake_case uniformly, with clear verbs like 'intercept', 'get', 'list', and 'send', making the naming predictable and easy to understand.

    Tool Count4/5

    With 23 tools, the count is slightly high but reasonable for the comprehensive scope of HTTP traffic interception across multiple platforms (browsers, mobile, Docker, terminals). Each tool serves a specific function, such as setup, activation, or management, though some consolidation might be possible without losing functionality.

    Completeness5/5

    The tool set provides complete coverage for HTTP Toolkit's domain, including interceptor activation/deactivation, traffic capture, platform-specific setup (Android, iOS, JVM), configuration retrieval, and server management. There are no obvious gaps; tools support the full lifecycle from setup to shutdown, ensuring agents can handle all core workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive

    Resources