Skip to main content
Glama
lucasoeth

mitmproxy-mcp MCP Server

by lucasoeth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to mitmproxy-mcp MCP Server

No user-submitted related servers found.

    Related Servers

    • Datetime MCP Server

      bossjones
      F
      license
      C
      quality
      D
      maintenance
      This server enables users to store, manage, and summarize notes using a custom URI scheme, with functionality to add new notes and generate summaries with varying levels of detail.
      3
      -

    • my-mcp

      ovezthaking
      F
      license
      Not graded
      quality
      D
      maintenance
      A note management MCP server that enables users to store, retrieve, and summarize personal notes via a custom URI scheme. It provides tools for adding content and prompts for generating brief or detailed summaries of stored information.
      -

    • Obenan MCP Server

      Azhar-obenan
      F
      license
      B
      quality
      D
      maintenance
      A simple note storage and management system that allows users to add, access, and summarize notes through a custom URI scheme. Supports creating summaries with configurable detail levels and provides real-time resource change notifications.
      4
      -
    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.2/5.0

    Scored across 4 tools

    Disambiguation3/5

    The tools have some overlap that could cause confusion. 'get_flow_details' and 'list_flows' both retrieve HTTP flow data, with 'get_flow_details' focusing on method/URL/status and 'list_flows' providing headers/content/metadata—these boundaries are unclear and might lead to misselection. However, 'analyze_protection' and 'extract_json_fields' are clearly distinct, targeting bot protection analysis and JSON field extraction respectively.

    Naming Consistency4/5

    The naming is mostly consistent with a verb_noun pattern, using snake_case throughout. 'analyze_protection', 'extract_json_fields', and 'list_flows' follow this well, but 'get_flow_details' deviates slightly by using 'get' instead of a more descriptive verb like 'show' or 'retrieve', which is a minor inconsistency in an otherwise predictable set.

    Tool Count5/5

    With 4 tools, the count is well-scoped for a mitmproxy server focused on HTTP flow analysis. Each tool appears to serve a distinct purpose within this domain, such as listing flows, analyzing protections, and extracting data, making the set neither too sparse nor overloaded for the intended functionality.

    Completeness3/5

    The tool surface has notable gaps for a mitmproxy domain. It covers flow retrieval, protection analysis, and JSON extraction, but lacks operations for modifying or intercepting flows (e.g., add, edit, block), which are core to proxy functionality. Agents can work around this by using existing tools for analysis, but the absence of manipulation tools limits completeness.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources