AgentsbyTask

ToolsMCP

browser-devtools-mcp

Listed in the official MCP Registry with a hosted streamable-http endpoint and an installable npm package. Capabilities below are the publisher’s own description.

Type
MCP server
Publisher
serkan-ozal (GitHub)
Prerequisites
An MCP client that supports streamable-http. No credential header is declared in the registry record. Install browser-devtools-mcp from npm (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
Current version
0.9.1 · updated
Official links

Publisher’s description

Playwright browser & Node.js MCP. ARIA refs, screenshots, ref-based interactions.
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.

Listed for these tasks

TaskDocumented for this taskUnknownsWhy it is listed
Automate a web browserPublisher description mentions “browser”, “playwright”, “screenshots”.No connection check or task run. Capability is as described by the publisher.Rule browser-automation matched: “browser”, “playwright”, “screenshots”. 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

Remote endpoints
https://{your_mcp_server_host}/mcp (streamable-http)
Packages
browser-devtools-mcp (npm, stdio, 2 secret inputs)
Registry entry
Official MCP Registry record (JSON)
Namespace
io.github.serkan-ozal/browser-devtools-mcp

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