Skip to main content
Glama
SH-DaWushi

web-api-extractor

by SH-DaWushi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to web-api-extractor

No user-submitted related servers found.

    Related Servers

    • browser-for-ai

      icueth
      A
      license
      B
      quality
      B
      maintenance
      A CDP-native MCP server that lets AI agents drive a real Chrome browser with deep network/console inspection, robust page interaction, and the ability to reverse-engineer a site's API flow into runnable code with dependency chaining and replay verification.
      52
      41 npm
      3
      MIT

    • Web2Actions

      rashidrashiii
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with websites by capturing browser traffic and exposing them as named MCP tools, requiring no public API.
      Apache 2.0

    • paparazzi

      nicksenap
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that connects to your browser to capture screenshots, inspect console logs, network requests, and more via Chrome DevTools Protocol.
      3 npm
      2
      MIT

    • BrowserUse

      YisRime
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to control Chrome/Edge browsers via CDP, including page navigation, element interaction, snapshots, network debugging, script execution, and performance tracing.
      AGPL 3.0

    • js-reverse-mcp

      1600822305
      A
      license
      Not graded
      quality
      D
      maintenance
      A Chrome DevTools Protocol-based MCP server that enables AI coding assistants to control browsers for JavaScript debugging, reverse engineering, web scraping, and API debugging.
      690 npm
      1
      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

    C2.1/5.0

    Scored across 21 tools

    Disambiguation2/5

    Multiple tools overlap in purpose without descriptions, e.g., probe_login, http_login, open_browser_login all concern login but lack clarity; confirm_login, confirm_login_ready, and request_login_confirm_dialog have overlapping names and functions. Even described tools like confirm_login_ready and confirm_login could be confused for similar actions.

    Naming Consistency4/5

    Most tools follow a verb_noun snake_case pattern (e.g., analyze_traffic, start_capture, list_sessions, export_project). A few exceptions like http_login and confirm_login_ready deviate slightly, but overall the naming convention is consistent and predictable.

    Tool Count3/5

    21 tools is on the heavier side but not extreme. The server's scope (login, capture, diff, merge, generate) could justify this count, but many tools lack descriptions and some overlap, making the set feel bloated.

    Completeness3/5

    The server covers a full lifecycle from login and capture to diff, merge, and server generation. However, missing tools like list_endpoints or delete_endpoint create gaps, and 13 tools without descriptions make it hard to assess whether the surface is complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources