js-reverse-mcp tested by Argusic Runner

Attempt 1 of 3 · Runs with mocks · Argusic Score 92.0 of 100

all runs of js-reverse-mcpanti-detectionbrowser-automationcdpchrome-devtoolsdebuggingjavascript

Session recording

Loading recording...

Download the original recording · fingerprint e3b7e473a6799b00...

What the test found

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.

All 114 unit tests pass (3631ms). MCP server responds to JSON-RPC initialize on stdin/stdout with valid capabilities. No real browser was available, so end-to-end browser-automation verification was not possible — all browser interactions are mocked in test suite. The project builds and prints CLI help and version. Test suite uses sinon and in-memory stubs for Patchright/CDP classes.

Argusic installed js-reverse-mcp in 6 minutes and launched it; verification reached Verified with mock services. 3 of 3 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of js-reverse-mcp

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.

Error and fix timeline

No errors were recorded for this run.

Discussion