jshookmcp

What it does

jshookmcp (published on npm as @jshookmcp/jshook) gives an assistant a large toolkit for taking apart front-end and native software. It drives Chromium or Camoufox over the Chrome DevTools Protocol, captures and replays network traffic, runs a local HTTPS man-in-the-middle proxy with its own generated certificate authority, deobfuscates and unpacks JavaScript bundles, disassembles WebAssembly, and reaches into running processes for memory scans, hooks and breakpoints. It also bridges to outside tools such as Frida, Ghidra, IDA and Burp Suite, and covers Android APK triage, decompilation and emulation of ARM64 shared libraries.

Version 0.4.2 registers 735 tools in 36 domains. To keep the tool list from swamping the model, it starts in the `search` profile by default, which registers only 8 meta tools at start-up (according to its configuration reference); the assistant finds tools with `search_tools` and turns on whole domains with `activate_domain` or runs a tool through `call_tool`. Setting `MCP_TOOL_PROFILE` to `workflow` or `full` loads more up front; the README puts the full set at about 109K tokens of tool metadata.

It runs over stdio by default, one process per client. It can also run as a shared Streamable HTTP daemon on 127.0.0.1:3000/mcp, which several agents can use at once with separate sessions. It suits security researchers, CTF players and people studying how a web app, game or mobile app works.

What it needs

Node.js 22.22.2 or later (or 24.15+), run through npx. Browser tools need a Chromium browser (point `PUPPETEER_EXECUTABLE_PATH` at one if needed); Camoufox, Playwright, ONNX, Z3 and Binaryen are optional packages that the README's sample config skips with `npm_config_omit=optional`. The Frida, Ghidra, IDA and Burp Suite bridges need those programs installed and their bridge running separately. The shared HTTP daemon needs a clone of the repo built with pnpm 10.

Limits

Its security guide says process and memory tools work best on Windows; on Linux and macOS it points users to browser hooks, network capture, workflows and bridge-based analysis instead. `browse_extension_registry` and `install_extension` return an error unless `EXTENSION_REGISTRY_BASE_URL` is set (configuration reference). CAPTCHA tools do not detect a widget on their own: the caller passes values such as `taskKind` and `siteKey`, and the default provider is `manual`. In HTTP mode, requests are limited to 60 per minute by default, and binding beyond localhost requires `MCP_AUTH_TOKEN`. Its docs are mostly in Chinese.

Who it suits

It suits security researchers and reverse engineers who want one local server that covers the browser, network, bundle, WASM and native layers, and who are prepared to install extra tools for the deeper features. Its process memory, injection and MITM proxy tools reach well beyond a browser, so it is more than you need if you only want to automate pages or take screenshots; a browser-only server is a smaller install for that. It is a third-party project, not tied to any vendor, and its AGPL-3.0 licence matters if you plan to ship changes to it.