JS Reverse MCP
Related Servers
Alternatives to JS Reverse MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding assistants to debug and analyze JavaScript in web pages by managing scripts, breakpoints, network and WebSocket traffic, browser state, and local file inputs/outputs for continuous reverse-engineering workflows.241,322 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive Chrome browser debugging capabilities including DOM inspection, network monitoring, console logs, JavaScript execution, breakpoint debugging, and screenshot capture for AI-assisted frontend development.5MIT
- AlicenseCqualityDmaintenanceEnables AI assistants to connect to browser DevTools and backend debuggers for full-stack debugging, including frontend console, network, performance, and backend log analysis.1617 npm7MIT
- AlicenseAqualityDmaintenanceEnables AI agents to attach to Chrome tabs, set breakpoints, inspect scope variables, evaluate expressions, and step through code using Chrome DevTools Protocol for runtime debugging.1843 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to debug JavaScript and TypeScript applications by connecting to Chrome DevTools Protocol-compatible debuggers, allowing them to set breakpoints, step through code, inspect variables, and evaluate expressions with full source map support.1816 npm2Apache 2.0
TDQS
Scored across 24 tools
Tools are organized around specific debugging actions, but many overlap in purpose (e.g., multiple breakpoint and pause/resume tools, multiple request inspection tools). While descriptions are precise, an agent could easily confuse which tool to use for a given step, especially with 24 tools.
Most tools follow a verb_noun pattern in snake_case (e.g., clear_network_requests, click_element). A few deviate slightly (e.g., 'break_on_xhr', 'get_paused_info'), but overall the naming is predictable and readable.
24 tools is on the higher side for a focused reverse engineering server. The set is comprehensive but some tools could be merged (e.g., clear_network_requests and clear_site_data are distinct but very similar). Still, each tool has a clear role, so the count is borderline but acceptable.
The tool surface covers all major aspects of JavaScript reverse engineering: network interception, source inspection, breakpoint management, page control, and evaluation. Minor gaps exist (e.g., no direct DOM query tool), but the set is largely complete for its purpose.