Skip to main content
Glama

Related Servers

Alternatives to js-reverse-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables AI coding assistants to debug and analyze JavaScript code in web pages through breakpoint debugging, function hooking, network analysis, and runtime inspection of scripts including minified code.
      24
      6,479 npm
      2,991
      Apache 2.0
    • A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to debug code and automate browsers using Chrome DevTools Protocol, supporting breakpoints, variable inspection, and replayable interaction recording.
      35
      56 npm
      18
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to debug frontend applications by providing direct access to browser DevTools, React state, DOM inspection, and runtime debugging capabilities. Bridges the gap between AI and complex web applications for autonomous debugging and issue resolution.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser through Chrome DevTools for automation, debugging, and performance analysis.
      2,058,331 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, network monitoring, and DOM interaction through Chrome DevTools Protocol.
      2,058,331 npm
      Apache 2.0

    TDQS

    A4.6/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: network, console, websocket, sources (list/search/get/save), breakpoints (set/list/remove/break_on_xhr), pause control, frame/page selection, and interaction. Descriptions actively route between near-neighbors (e.g. get_script_source vs save_script_source vs search_in_sources, get_request_initiator vs break_on_xhr), so an agent can reliably pick the right one.

    Naming Consistency4/5

    Consistent snake_case with a dominant verb_noun pattern (list_network_requests, get_script_source, remove_breakpoint, clear_site_data, select_frame). A few deviations — new_page (no verb), break_on_xhr (verb_prep_noun), step and pause_or_resume (bare/compound verbs) — but all remain readable and semantic.

    Tool Count4/5

    24 tools is on the heavy side, but the domain (CDP-level browser reverse engineering) genuinely spans network, debugger, source, frame, page, and interaction surfaces, and each tool maps to a real capability with no filler. Slightly over a lean set but reasonable for the scope.

    Completeness4/5

    Coverage of the reverse-engineering core is strong: HTTP and WebSocket evidence, console, source discovery/inspection, code and XHR breakpoints, pause/step, and site/network reset. Gaps exist on the interaction side (no text input/keypress/hover/scroll or wait-for-selector), and breakpoints are text- or URL-based only (no line/column breakpoint), which agents must work around via evaluate_script or click_element.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues