js-reverse-mcp
AI Agent-first JS 逆向 MCP Server：有头 Chrome 调试、断点、网络/WebSocket 分析、Patchright 反检测，可选 CloakBrowser。
Runs with mockssource: GitHubTypeScriptApache-2.0commit bf7dc506e874
TypeScript, Apache-2.0 licensed. The project labels itself: anti detection, browser automation, cdp, chrome devtools, debugging, javascript, mcp and mcp server.
js-reverse-mcp runs, with stand-ins for the services it depends on. An Argusic agent installed it in 6 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The js-reverse-mcp v4.0.5 TypeScript project compiles to JavaScript, its full test suite of 114 tests passes, and the MCP server binary responds to JSON-RPC initialize on stdin/stdout. A Node.js v22.12.0 upgrade was applied (portable) and the cloakbrowser optional dependency was installed. Google Chrome is not installed on the runner, so end-to-end browser automation could not be verified.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No Google Chrome/chromium binary available on system; patchright install chrome needs root for apt deps3 minutes
- Node.js v18.19.1 installed but project requires ^20.19.0 || ^22.12.0 || >=232 minutes
- npm install without optionalDependencies leaves cloakbrowser missing; tsc fails on src/cloak.ts1 minute
- Install time
- 6 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm test: 114 pass, 0 fail. node build/src/index.js --version prints '4.0.5'. node build/src/index.js --help prints all CLI options. echo '{"jsonrpc":"2.0","method":"initialize",...}' | node build/src/index.js returns valid MCP server info.
- Model tokens used
- 49,196
- Exact commit tested
- bf7dc506e874
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/bin/sh -lc 'cd /work/repo && export PATH="/tmp/node-v22.12.0-linux-x64/bin:$PATH" && echo '"'{\"js…
succeeded in 305ms:
{"result":{"protocolVersion":"2025-11-25","capabilities":{"logging":{},"tools":{"listChanged":true}…
Now I have the complete picture. Let me compile the final structured report.
exec
/bin/sh -lc 'echo "start_time=$(date +%s)"' in /work/repo
succeeded in 0ms:
start_time=1790957948
Now I have all the data. Here's the final result:
tokens used
49,196
Now I have all the data. Here's the final result:Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 6 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.02 |
Topics (from GitHub)
anti-detectionbrowser-automationcdpchrome-devtoolsdebuggingjavascriptmcpmcp-serverpatchrightreverse-engineeringwebsocket
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/js-reverse-mcp)Questions
- Does js-reverse-mcp run?
- js-reverse-mcp runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 6 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test js-reverse-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bf7dc506e874. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test js-reverse-mcp?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does js-reverse-mcp take to install?
- 6 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does js-reverse-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing js-reverse-mcp?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for js-reverse-mcp?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.