Skip to main content
Glama
jenn619

js-reverse-mcp

by jenn619
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to js-reverse-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • 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

    • wechat-miniprogram-mcp

      littlehack
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables dynamic reverse engineering and debugging of WeChat MiniProgram JavaScript through the Chrome DevTools Protocol, letting AI agents enumerate and search scripts, set breakpoints, step through paused frames, trace function calls, hook miniprogram APIs such as wx.request, and capture network requests to analyze encryption, signing, and anti-scraping logic. It also works against Chrome, Node.js, and Electron runtimes, with tools for extracting code bundles and page business logic.
      11 npm
      MIT
    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

    A3.7/5.0

    Scored across 31 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with well-defined prefixes (browser_, crypto_, generate_, js_, network_, page_, runtime_, script_) that group related functions. There is minimal overlap; for example, crypto_analyze_param and crypto_auto_detect target different aspects (specific parameter vs. full scan).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores, using prefixes to indicate domain (e.g., browser_launch, crypto_auto_detect, network_get_requests). No mixed conventions or ambiguous verbs.

    Tool Count4/5

    31 tools is relatively high, but the domain of JavaScript reverse engineering is inherently complex, requiring tools for browser control, crypto analysis, JS analysis, network interception, script generation, and testing. Each tool justifies its existence, though some consolidation might be possible (e.g., crypto_analyze_param and crypto_auto_detect could merge).

    Completeness5/5

    The tool set covers the full workflow: launch browser, navigate, intercept network, analyze JS, detect crypto, extract keys, generate encryption/decryption/brute-force scripts, and test them. No obvious gaps; even edge cases like hooking functions and tracing call chains are included.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources