Skip to main content
Glama
numb747

mitmweb-mcp

by numb747
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mitmweb-mcp

No user-submitted related servers found.

    Related Servers

    • interceptpilot-mcp

      AndersonAlpin
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read sanitized test context, captured requests, rules, and logs from the InterceptPilot Chrome extension, and to propose or run actions such as enabling mocks, importing collections, or capturing tabs, all locally over a secure WebSocket.
      10 npm
      MIT

    • 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.
      5 npm
      MIT

    • playwriter

      remorses
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects to your running Chrome browser, enabling AI agents to automate it via Playwright API with existing logins and extensions.
      2,513 npm
      3,922
      MIT
    • colab-mcp by googlecolab

      colab-mcpofficial

      googlecolab
      A
      license
      A
      quality
      D
      maintenance
      Bridges a local agent to a Colab session in the browser, enabling seamless interaction with Colab from local clients.
      1
      1,088
      Apache 2.0
    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

    A4.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: status checks connectivity, flow_stats provides an overview, inspect_flow gives full detail, detect_auth scans authentication, list_flows lists flows, get_content fetches full bodies, search_flows performs full-text search, diff_flows compares requests, generate_code produces scripts, and replay_flow replays requests. No two tools overlap in intent; even get_content and inspect_flow differ in scope (full vs. preview).

    Naming Consistency5/5

    All tool names follow a consistent lowercase_snake_case convention with a verb-first pattern (inspect_flow, detect_auth, list_flows, get_content, search_flows, diff_flows, generate_code, replay_flow) and a few exceptions like status and flow_stats that still fit the overall style. No mixing of camelCase or different naming schemes.

    Tool Count5/5

    With 10 tools, the set is well-scoped for a traffic capture and analysis server. Each tool covers a distinct aspect of the workflow: connectivity, overview, inspection, auth detection, listing, body retrieval, search, diffing, code generation, and replay. The count feels neither thin nor bloated.

    Completeness5/5

    The tool surface covers the full lifecycle of working with captured HTTP traffic: connect, summarize, inspect, search, compare, generate code, and replay. It also includes advanced features like auth detection and body extraction. There are no obvious dead ends—each tool feeds into the next, and the domain is thoroughly addressed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources