mcp-chrome tested by Argusic Runner

What the test found

The monorepo builds successfully (packages/shared, app/chrome-extension, app/native-server), all 642 tests pass, the CLI responds to help/doctor commands, and the MCP stdio server starts without errors.

All 642 tests pass (641 vitest + 1 jest). The mcp-chrome-bridge CLI and MCP server start correctly. The project requires a Chrome browser with the extension installed for full functionality, but both packages (chrome-extension, native-server) build and their test suites pass in this headless container environment. No third-party credentials are needed. The wasm-simd package requires wasm-pack which is not available, but it is filtered out from the main build and is not needed for testing or the native-server runtime.

Argusic installed mcp-chrome in 8 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 mcp-chrome

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.