Skip to main content
Glama
wukaka

camoufox-jsreverser-mcp

by wukaka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to camoufox-jsreverser-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      514
      MIT

    • JS Reverse MCP

      NoOne-hub
      A
      license
      C
      quality
      B
      maintenance
      An MCP server for JavaScript reverse engineering that enables AI to perform browser debugging, script analysis, and automated hook injection. It streamlines complex workflows like deobfuscation, network tracing, and risk assessment through direct browser integration.
      35
      21 npm
      1,020
      Apache 2.0

    • js-reverse-mcp

      yuanchuangith
      A
      license
      Not graded
      quality
      C
      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.
      722 npm
      Apache 2.0

    • 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.
      722 npm
      9
      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.6/5.0

    Scored across 84 tools

    Disambiguation2/5

    Many tools overlap in purpose, such as multiple injectors (inject_hook, inject_preload_script, inject_stealth, inject_stealth_hook), breakpoint setters (set_breakpoint, set_breakpoint_on_text), and search tools (search_in_scripts, search_in_sources, find_in_script). Convenience wrappers like hook_function, trace_function, and unhook_function add ambiguity. An agent would struggle to select the correct tool.

    Naming Consistency3/5

    Tool names mostly follow verb_noun in snake_case (e.g., analyze_target, list_scripts), but inconsistencies exist: mix of 'get_' vs 'list_' for retrieval, 'find_' vs 'search_' for searches, and some compound names (break_on_xhr, type_text) break the pattern. Overall moderately consistent but deviations are notable.

    Tool Count1/5

    84 tools is far beyond typical MCP server scope (3-15 tools). This extreme count suggests scope creep, many niche utilities, and overlapping functionality. The number makes the server unwieldy and poorly scoped for its stated purpose.

    Completeness3/5

    The tool set covers a broad range of reverse engineering tasks (debugging, script analysis, deobfuscation, stealth, networking, sessions). However, gaps exist: limited DOM manipulation (only click, type_text), no storage value access, and many tools marked as v1 or M3, indicating incomplete implementation. Comprehensive but not fully polished.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources