Skip to main content
Glama
NoOne-hub

JS Reverse MCP

by NoOne-hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to JS Reverse MCP

No user-submitted related servers found.

    Related Servers

    • JS Reverse MCP

      a0yark
      A
      license
      Not graded
      quality
      D
      maintenance
      A JavaScript reverse engineering MCP server that enables AI coding assistants to debug and analyze JavaScript code in web pages.
      822 npm
      7
      Apache 2.0

    • js-reverse-mcp

      yuanchuangith
      A
      license
      Not graded
      quality
      B
      maintenance
      An AI-native JavaScript reverse engineering MCP server for debugging, locating, saving, and replaying web page JavaScript behavior. Includes anti-detection mechanisms to handle strong anti-bot sites.
      822 npm
      Apache 2.0

    • camoufox-reverse-mcp

      WhiteNightShadow
      A
      license
      B
      quality
      A
      maintenance
      An anti-detection browser MCP server designed for JavaScript reverse engineering through the Camoufox engine. It enables AI assistants to perform dynamic debugging, function hooking, and network interception while bypassing sophisticated bot detection mechanisms.
      39
      505
      MIT

    • 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.
      822 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.9/5.0

    Scored across 35 tools

    Disambiguation2/5

    Many tools have overlapping purposes: search_in_scripts and search_in_sources both search code, manage_reverse_task/start_reverse_task/orchestrate_reverse_task all handle task lifecycle, and recommend_next_step/explain_reverse_stage both provide guidance. This overlap makes it difficult for an agent to reliably select the correct tool.

    Naming Consistency4/5

    The vast majority of tools follow a verb_noun convention (e.g., collect_code, analyze_source_maps, navigate_page), but there are minor deviations like network_request (noun only) and search_in_scripts/search_in_sources which use a different structure. Overall, the pattern is consistent enough.

    Tool Count2/5

    With 35 tools, the server is heavily over-scoped. Many tools are narrowly specialized and could be consolidated (e.g., multiple export tools, multiple task-management entry points), and the count exceeds the recommended range, adding unnecessary selection overhead.

    Completeness3/5

    The set covers a broad reverse-engineering workflow including probing, code collection/search, network tracing, task management, and exporting. However, it references get_script_source which is not one of the tools, causing a dead end for viewing full script context. Other gaps include lack of direct script execution or editing capabilities.

    Maintenance

    ActivityInactive
    ResponsivenessWithin a week

    Resources