jshookmcp
js hook toolkit that all you need
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/vmoranv/jshookmcp with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/vmoranv/jshookmcp'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/vmoranv--jshookmcp)HTML
<a href="/listings/vmoranv--jshookmcp"><img src="/api/listings/vmoranv--jshookmcp/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
No global install needed — add to your MCP client config and you're ready.
**Claude Desktop / Cursor (`claude_desktop_config.json`):**
{
"mcpServers": {
"jshook": {
"command": "npx",
"args": ["-y", "@jshookmcp/jshook@latest"],
"env": {
"MCP_TOOL_PROFILE": "search",
"npm_config_omit": "optional"
}
}
}
}*(Windows: use `npx.cmd` absolute path if `npx` is not found.)*
This lightweight configuration skips optional ONNX, Z3, Binaryen, Camoufox, and Playwright packages. Remove `npm_config_omit` when those full-profile runtimes are required.
Share one daemon across multiple agents
The default stdio configuration starts one full jshook process per MCP host. To share the embedding model, browser runtime, and caches, start one local Streamable HTTP daemon:
pnpm build pnpm daemon
Vector search defaults to off for per-client stdio processes and on (lazy-loaded) for the shared HTTP daemon. Set `SEARCH_VECTOR_ENABLED=false` when lexical search is sufficient.
Then point every MCP client at `http://127.0.0.1:3000/mcp` using its HTTP/URL server configuration. Each client receives its own MCP session and response route while heavyweight runtime resources remain in one process. Keep the default loopback bind; set `MCP_AUTH_TOKEN` before exposing the endpoint beyond localhost.
Promote a profile as the task grows
{
"env": {
"MCP_TOOL_PROFILE": "search" // start here, ~3K tokens of metadata
}
}Switch `MCP_TOOL_PROFILE` to `workflow` once you start chaining composite scripts, or to `full` when you need every tool. `coverage_report` shows the active set on demand.
---
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 316 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- <div align="center">
- <img src="docs/public/favicon.png" width="96" alt="@jshookmcp/jshook" />
- # @jshookmcp/jshook
- [](LICENSE)
- [](https://nodejs.org/)
- [](https://www.typescriptlang.org/)
- [](https://modelcontextprotocol.io/)
- [](https://pnpm.io/)
- <a href="https://trendshift.io/repositories/31180?utm_source=trendshift-badge&utm_medium=badge&utm_campaign=badge-trendshift-31180" target="_blank" rel="noopener noreferrer"><img src="https://trendshift.io/api/badge/trendshift/repositories/31180/daily?language=TypeScript" alt="vmoranv%2Fjshookmcp | Trendshift" width="250" height="55"/></a>
- **A search-first, profile-aware reverse-engineering workspace for AI agents.**
- **Hook the page, capture the network, deobfuscate the bundle, disassemble the WASM, instrument the process — and let one MCP server keep the whole attack surface in reach without drowning the model in schemas.**
- English · [中文](./README.zh.md)
- <p align="center">
- <a href="https://github.com/vmoranv/jshookmcp/stargazers">
- <img src="https://img.shields.io/github/stars/vmoranv/jshookmcp?style=for-the-badge" alt="Stars" />
- </a>
- <a href="https://github.com/vmoranv/jshookmcp/network/members">
- <img src="https://img.shields.io/github/forks/vmoranv/jshookmcp?style=for-the-badge" alt="Forks" />
- </a>
- <a href="https://github.com/vmoranv/jshookmcp/releases">
- <img src="https://img.shields.io/github/v/tag/vmoranv/jshookmcp?style=for-the-badge&sort=semver" alt="Latest Release" />
- </a>
- <a href="LICENSE">
- <img src="https://img.shields.io/badge/license-AGPLv3-red?style=for-the-badge" alt="License" />
- </a>
- </p>
- <p align="center">
- <!-- npm badge: re-add once @jshookmcp/jshook is published -->
- <a href="https://nodejs.org/">
- <img src="https://img.shields.io/badge/node-22.22.2%2B-brightgreen?style=for-the-badge&logo=node.js" alt="Node.js 22.22.2+" />
- </a>
- <a href="https://www.typescriptlang.org/">
- <img src="https://img.shields.io/badge/TypeScript-strict-3178C6?style=for-the-badge&logo=typescript&logoColor=white" alt="TypeScript strict" />
- </a>
- <a href="https://modelcontextprotocol.io/">
- <img src="https://img.shields.io/badge/MCP-current-8A2BE2?style=for-the-badge" alt="MCP current" />
- </a>
- </p>
- <p align="center">
- <a href="#what-makes-jshook-different">What's different</a> ·
- <a href="#capability-overview">Capabilities</a> ·
- <a href="#use-cases">Use cases</a> ·
- <a href="#highlights">Highlights</a> ·
- <a href="#transport-and-deployment">Transport</a> ·
- <a href="#registry-snapshot">Registry</a> ·
- <a href="#architecture">Architecture</a> ·
- <a href="#build-from-source">Build</a>
- </p>
- <p align="center">
- <a href="https://vmoranv.github.io/jshookmcp/">Documentation</a> ·
- <a href="https://vmoranv.github.io/jshookmcp/guide/getting-started.html">Getting Started</a> ·
- <a href="https://vmoranv.github.io/jshookmcp/guide/configuration.html">Configuration</a> ·
- <a href="https://vmoranv.github.io/jshookmcp/reference/">Tool Reference</a>
- </p>
- ---
- </div>
- ## What makes jshook different
- Most MCP servers for JS analysis expose a handful of hand-rolled tools or wrap a single browser engine. jshook is closer to an **operating system for front-end reverse engineering** — 36 self-discovered domains, a search-first meta-tool that keeps token cost under control, and runtime recovery that survives broken pages and dropped sessions:
- - **Search-first, profile-aware.** The `search` profile loads about 3K tokens of tool metadata; the `full` profile exposes all 736 tools at around 109K tokens (measured 2026-10-10 — this figure scales with the tool count, so re-measure it when the catalog grows). Agents move between them as the task grows — `search` → `workflow` → `full` — instead of drowning in schemas from the first turn.
- - **Runtime recovery and session isolation.** Streamable HTTP sessions restore activated domains, browser attach state, and coverage state after reconnects; per-client browser-side state stays isolated so two agents cannot trample each other's CDP sessions.
- - **Full-stack browser automation.** Chromium and Camoufox via CDP with anti-detection, an explicit-input CAPTCHA solver (no built-in page/feature probing), a self-signed HTTPS interception CA on demand, and HTTP/2 frame building.
- - **Real reverse engineering, not string searches.** WASM disassembly via wabt (`wasm2wat` / `wasm-decompile` / `wasm-objdump`), Frida/Ghidra/IDA bridges, native FFI scanning, hardware breakpoints, PE introspection, GraphQL/Burp Suite proxy bridges, and AST transforms — not a single regex call wrapped as a tool.
- - **Dynamic extensibility.** Hot-reload plugins, declarative workflows, and auto-discovery keep the server growing without a redeploy.
- ---
- ## Capability overview
- A scan of what's in the box. Each row links to the detailed [Capability overview](#capability-overview) below.
- | Area | Highlights |
- | --- | --- |
- | **Tool profiles** | `search` (~3K tokens, BM25 + hybrid vector ranking) · `workflow` (composite scripts) · `full` (all 736 tools) |
- | **Browser automation** | Chromium and Camoufox · CDP attach to existing targets · anti-detection presets · explicit-input CAPTCHA solver · popup, download, permission, and protocol interceptors |
- | **Network interception** | HTTP/1.1 + HTTP/2 frame building · MITM proxy with auto-generated CA · WebSocket capture · GraphQL introspection helpers · Burp Suite bridge |
- | **JS hooks and analysis** | LLM-powered deobfuscation · crypto routine detection · AST comprehension · source-map reconstruction · script/scriptlet extraction and replay |
- | **WASM reverse engineering** | wabt disassembly / C transpilation (`wasm2wat` / `wasm-decompile` / `wasm-objdump` / `wasm2c`) · Binaryen `wasm-opt` · pure-TS section parser · import/export listing · section-grouped string extraction with name-section recovery · function-level binary diff · obfuscation detection · function- and basic-block-level instrumentation |
- | **Process and memory forensics** | Native FFI scanning · cross-reference graphs · hardware breakpoints · PE introspection · live process attach · memory read/write with region guards |
- | **Binary instrumentation** | Frida bridge · Ghidra and IDA bridges · syscall hooking · TLS keylog and session tooling · Mojo IPC analysis |
- | **Android and APK analysis** | APK static triage · manifest dump and query · apktool decode / build · jadx decompilation and code search · DEX scanning · native library listing · APK signing · unidbg emulation · runtime DEX dump |
- | **Native runtime** | Native emulator for foreign-architecture samples · platform introspection · Mojo IPC · Dart Inspector · ADB bridge for on-device traffic |
- | **Encoding and transform** | URL/Base64/Hex/JWT/Protobuf encoders · AST transforms · streaming decode pipelines |
- | **Coordination** | Background task queue with progress, cancellation, and async modes · multi-agent coordination · coverage reports |
- | **Schema-first meta tools** | `describe_tool` · `call_tool` with argument validation · `coverage_report` · `search_tools` |
- | **Pluggable extension registry** | Hot-reload plugins · declarative workflows · auto-discovered domains |
- ---
- ## Use cases
- | Scenario | What you do | Domains involved |
- | --- | --- | --- |
- | Skim a minified bundle | `search_tools` → `deobfuscate` → `search_in_scripts` → `understand_code` | `core` |
- | Reverse a CAPTCHA challenge | Drive a Camoufox page → screenshot → solve with explicit input → replay | `browser`, `canvas` |
- | Capture and replay an OAuth flow | `proxy_start` (auto CA) → `network_get_requests` → `graphql_introspect` → `graphql_replay` | `proxy`, `network`, `graphql` |
- | Reverse a WASM crypto routine | `wasm_dump` → `wasm_disassemble` → `generate_hooks` → `memory_breakpoint` | `wasm`, `binary-instrument`, `memory` |
- | Triage a suspicious APK | `apk_static_triage` → `apk_manifest_dump` → `jadx_decompile` → `dex_scan_file` | `binary-instrument` |
- | Recover a dropped browser session | Reconnect Streamable HTTP → restore activated domains and browser state | `browser`, `coordination` |
- | Audit a Node process for credentials | `process_list` → `memory_scan_filtered` → `binary_strings_extract` | `process`, `memory`, `binary-instrument` |
- | Build a custom workflow | `list_extension_workflows` → `run_extension_workflow` | `workflow`, `extension-registry` |
- | Hook a function in a live process | `frida_spawn` → `frida_attach_interceptor` → `frida_run_script` → `frida_enumerate_functions` | `binary-instrument` |
- ---
- ## Quick start
- No global install needed — add to your MCP client config and you're ready.
- **Claude Desktop / Cursor (`claude_desktop_config.json`):**
- ```json
- {
- "mcpServers": {
- "jshook": {
- "command": "npx",
- "args": ["-y", "@jshookmcp/jshook@latest"],
- "env": {
- "MCP_TOOL_PROFILE": "search",
- "npm_config_omit": "optional"
- }
- }
- }
- }
- ```
- *(Windows: use `npx.cmd` absolute path if `npx` is not found.)*
- This lightweight configuration skips optional ONNX, Z3, Binaryen, Camoufox, and Playwright
- packages. Remove `npm_config_omit` when those full-profile runtimes are required.
- **This is a Node.js service, not a browser library.** It runs over stdio or a local
- Streamable HTTP daemon (`engines.node: ^22.22.2 || ^24.15.0 || >=26.0.0`); it is not
- intended for bundling into a web page. The published tarball is ~1.45 MB gzipped /
- ~5 MB unpacked (358 files, mostly `dist/`). Bundle-size sites such as Bundlephobia
- report a much smaller tree-shaken figure (~48 KB gzip) because they analyze the
- `dist/index.mjs` entry as if it were a browser bundle — that number does not describe
- the installed CLI/server. There are no install-time lifecycle scripts and no bundled
- native binaries; native runtimes are optional and loaded on demand.
- ### Share one daemon across multiple agents
- The default stdio configuration starts one full jshook process per MCP host. To share the
- embedding model, browser runtime, and caches, start one local Streamable HTTP daemon:
- ```bash
- pnpm build
- pnpm daemon
- ```
- Vector search is on by default on every transport — a lightweight static model whose catalog
- embeddings persist to disk, loaded lazily and released when idle. Set `SEARCH_VECTOR_ENABLED=false`
- when lexical search is sufficient.
- Then point every MCP client at `http://127.0.0.1:3000/mcp` using its HTTP/URL server
- configuration. Each client receives its own MCP session and response route while heavyweight
- runtime resources remain in one process. Keep the default loopback bind; set `MCP_AUTH_TOKEN`
- before exposing the endpoint beyond localhost.
- ### Promote a profile as the task grows
- ```jsonc
- {
- "env": {
- "MCP_TOOL_PROFILE": "search" // start here, ~3K tokens of metadata
- }
- }
- ```
- Switch `MCP_TOOL_PROFILE` to `workflow` once you start chaining composite scripts, or to `full`
- when you need every tool. `coverage_report` shows the active set on demand.
- ## Telemetry (on by default)
- jshookmcp ships opt-out OpenTelemetry instrumentation. With **zero configuration** it exports
- minimal tool-call and search-usage signals over OTLP/HTTP to the project maintainer's ingress
- (`https://telemetry.614447.xyz`), identified only by an anonymous, locally generated
- `install.id`. No tool arguments, response bodies, host names, user names, or IPs are collected by
- default; query text is truncated to 64 characters and credential-like keys are scrubbed.
- This outbound traffic happens even when you invoke no tool, so it is disclosed here rather than
- buried in a guide. To disable it entirely (zero network, zero overhead) or redirect it to your own
- backend, set these in the MCP server process environment:
- ```bash
- JSHOOK_OBSERVABILITY_EXPORTER=none # turn telemetry off entirely
- OTEL_EXPORTER_OTLP_ENDPOINT=<your-collector> # or ship to your own OTLP backend
- OTEL_EXPORTER_OTLP_HEADERS="authorization=Bearer <token>"
- ```
- For the full data-minimisation table and per-signal controls (`JSHOOK_OTLP_QUERY_TEXT`,
- `JSHOOK_OTLP_TOOL_ARGS`), see the [Telemetry guide](https://vmoranv.github.io/jshookmcp/guide/telemetry.html).
- ---
- ## Highlights
- - **Profile ladder.** Start in `search` (~3K tokens of metadata); promote to `workflow` when chaining composite scripts; escalate to `full` only when every tool is actually needed. `coverage_report` shows what's active on demand.
- - **Meta tools.** `describe_tool` returns the JSON Schema; `call_tool` validates arguments before invocation; every tool ships with `readOnlyHint` / `destructiveHint` / `idempotentHint` / `openWorldHint`.
- - **Browser automation.** Chromium and Camoufox via CDP, attach to existing targets, anti-detection presets, popup/download/permission interceptors, explicit-input CAPTCHA solver, JS/CSS injection at three document phases, persisted coverage across reconnects.
- - **Network interception.** Auto-generated HTTPS interception CA, HTTP/1.1 + HTTP/2 frame building, WebSocket capture, GraphQL helpers, Burp Suite bridge — all on the same MCP tool surface.
- - **Reverse engineering.** wabt WASM disassembly (`wasm2wat` / `wasm-decompile` / `wasm-objdump`) and Binaryen `wasm-opt`, Frida/Ghidra/IDA bridges, hardware breakpoints, native FFI scanning, PE introspection, syscall hooking, AST transforms, source-map reconstruction.
- - **Session recovery.** Streamable HTTP transport restores activated domains, browser attach state, and coverage state after reconnects; browser-side state is isolated per client.
- - **Plugins and workflows.** Drop a directory, get a domain. Write a YAML pipeline, run it as one tool. The registry self-discovers.
- ---
- ## Transport and deployment
- The server supports two transports out of the box.
- | Transport | When to use | Notes |
- | --- | --- | --- |
- | **stdio** | Default for Claude Desktop, Cursor, and other single-host clients | One full process per MCP host; lightweight profile recommended |
- | **Streamable HTTP** | Multiple agents sharing the embedding model, browser runtime, and caches | Loopback bind by default; set `MCP_AUTH_TOKEN` before exposing externally |
- Both transports expose the same tool surface. `coverage_report` shows which domains are
- activated in each session — long-running sessions restore browser attach state, coverage state,
- and tool activations across reconnects.
- For production deployments see the [Security and Production guide](https://vmoranv.github.io/jshookmcp/operations/security-and-production.html).
- ---
- ## Recent runtime notes
- - HTTP transport now multiplexes independent MCP sessions and restores runtime state after reconnects.
- - `proxy_start` auto-generates a local HTTPS interception CA when needed.
- - Browser CAPTCHA solving is now explicit-input driven: pass `taskKind`, `siteKey`, `imageBase64`, `callbackName`, and `responseSelector` as needed. Built-in widget/page signature probing is intentionally not used.
- ---
- ## Registry snapshot
- The built-in surface below is generated from the runtime registry and checked in CI.
- <!-- metadata-sync:start -->
- - Package version: `0.4.7`
- - Built-in tools: `736`
- - Domains: `adb-bridge`, `binary-instrument`, `browser`, `canvas`, `coordination`, `core`, `cross-domain`, `dart-inspector`, `debugger`, `encoding`, `exploit-dev`, `extension-registry`, `graphql`, `instrumentation`, `maintenance`, `memory`, `mojo-ipc`, `native-bridge`, `native-emulator`, `network`, `platform`, `process`, `protocol-analysis`, `proxy`, `session`, `sourcemap`, `streaming`, `syscall-hook`, `tasks`, `tls-inspector`, `trace`, `transform`, `v8-inspector`, `wasm`, `webgpu`, `workflow`
- - Note: this snapshot is generated from the runtime registry; do not edit the counts by hand.
- <!-- metadata-sync:end -->
- > **[View the complete Tool Reference ↗](https://vmoranv.github.io/jshookmcp/reference/)**
- ---
- ## Architecture
- - **Runtime registry** — domains auto-discovered via `manifest.ts`; add a domain by creating one file.
- - **Lazy initialization** — handlers instantiated on first call, not at startup.
- - **BM25 + vector search** — `search_tools` meta-tool with hybrid ranking and adaptive weights.
- - **MCP `ToolAnnotations`** — every tool carries `readOnlyHint` / `destructiveHint` / `idempotentHint` / `openWorldHint`.
- - **Profile ladder** — `search` (~3K tokens) → `workflow` (composite scripts) → `full` (all 736 tools).
- - **Transport symmetry** — stdio and Streamable HTTP expose the same surface; sessions are isolated per client.
- See the [Architecture guide](https://vmoranv.github.io/jshookmcp/guide/best-practices.html) and [Configuration reference](https://vmoranv.github.io/jshookmcp/guide/configuration.html) for the canonical details.
- ---
- ## Build from source
- Requirements: Node.js 22.22.2+, pnpm 10.x.
- ```bash
- pnpm install
- pnpm build
- pnpm start # run the built server from dist/
- pnpm dev # run from source under tsx watch
- pnpm check # drift guards (metadata + openapi + domain + event contracts) + lint + format check + typecheck + unit tests
- pnpm test # Vitest unit suites
- pnpm test:e2e # end-to-end browser/tooling suites
- pnpm daemon # run the Streamable HTTP daemon after build
- ```
- Native helpers are bundled via `pnpm build`; on first run the server may download optional
- runtimes (ONNX, Z3, Binaryen, Camoufox, Playwright) depending on the profile.
- ---
- ## Project stats
- <div align="center">
- <a href="https://www.star-history.com/?repos=vmoranv%2Fjshookmcp&type=date&legend=top-left">
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/image?repos=vmoranv/jshookmcp&type=date&legend=top-left" />
- <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/image?repos=vmoranv/jshookmcp&type=date&legend=top-left" />
- <img alt="Star History Chart" src="https://api.star-history.com/image?repos=vmoranv/jshookmcp&type=date&legend=top-left" />
- </picture>
- </a>
- 
- </div>
- ---
- ## License
- [AGPLv3](./LICENSE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.