cdp-bridge-mcp tested by Argusic Runner

Attempt 1 of 3 · Unverified · Argusic Score 80.0 of 100

all runs of cdp-bridge-mcpbrowser-automationchrome-extensionmcp-servermodel-context-protocol

Session recording

Loading recording...

Download the original recording · fingerprint 40f9e98fe7430eeb...

What the test found

cdp-bridge MCP server installs cleanly from source, runs on both stdio and streamable-http transports, lists 12 MCP tools, and enforces token-based access control; browser automation requires a Chrome browser with the companion extension.

No errors encountered. The project has no test suite (per CLAUDE.md). The server starts on both stdio and streamable-http transports, responds to MCP protocol initialize/tools/list/tools/call correctly, returns empty tab lists gracefully without a connected browser extension, and enforces token-based auth (401/403/200). A real Chrome browser with the extension is required for full end-to-end verification, which is not available in this container.

Argusic installed cdp-bridge-mcp in 3 minutes and launched it; verification reached Nothing verified.

Unverifiedall runs of cdp-bridge-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