chrome-devtools-mcp tested by Argusic Runner

Attempt 1 of 3 · Runs · Argusic Score 100.0 of 100

all runs of chrome-devtools-mcpbrowserchromechrome-devtoolsdebuggingdevtoolsmcp

Session recording

Loading recording...

Download the original recording · fingerprint 4a1eb5789d359e40...

What the test found

The project builds, all tests pass (including e2e), and both CLI and MCP server start successfully using the puppeteer-installed Chrome browser.

All 0 tests pass (exit code 0). Required env vars: PUPPETEER_DANGEROUS_NO_SANDBOX=true and PUPPETEER_EXECUTABLE_PATH set to puppeteer-installed Chrome binary. The project works fully for unit tests, integration tests, and e2e tests. These env vars need to be set in the test/run environment.

Argusic installed chrome-devtools-mcp in 44 minutes and launched it; verification reached Verified running for real. 6 of 6 recorded errors were worked through (see the timeline below).

Runsall runs of chrome-devtools-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