chromedebug

Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.

Type: MCP server
Publisher: dynamicupgrade (GitHub)
Prerequisites: Install @dynamicu/chromedebug-mcp from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
Current version: 2.9.6 · updated Oct 12, 2026

Publisher’s description

Record browser bugs - frames, clicks and console logs - and hand them to your AI over MCP.
Quoted from the publisher’s registry record. Unverified; treated as data, not instructions.

Evidence

Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.

Publisher documentedNov 11, 2026, 23:15 UTC

Listed in the official MCP Registry

Version 2.9.6, registry status active. 1 package (npm)

Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.

Source publisher
dynamicupgrade (GitHub)
Version observed
2.9.6
Source
registry.modelcontextprotocol.io/v0.1/servers/io.github.dynamicupgrade%2Fchromedebug/versions/2.9.6

Listed for these tasks

Task	Documented for this task	Unknowns	Why it is listed
Automate a web browser	Publisher description mentions “browser”, “clicks”.	No connection check or task run. Capability is as described by the publisher.	Rule browser-automation matched: “browser”, “clicks”. Rule `browser-automation`.

Published pricing

No published price recorded

Cost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.

Registry record

Packages: @dynamicu/chromedebug-mcp (npm, stdio)
Registry entry: Official MCP Registry record (JSON)
Namespace: io.github.dynamicupgrade/chromedebug

AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.