ToolsMCP
WebRun Browser Automation
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- webrun.ai
- Prerequisites
- An MCP client that supports streamable-http. The publisher declares a required credential header.
- Current version
- 1.0.2 · updated
- Official links
Publisher’s description
Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.
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 in the official MCP Registry
Version 1.0.2, registry status active. 1 remote endpoint (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- webrun.ai
- Version observed
- 1.0.2
- Source
- registry.modelcontextprotocol.io/v0.1/servers/ai.webrun%2Fwebrun/versions/1.0.2
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Automate a web browser | Publisher description mentions “browser”, “automation”. | No connection check or task run. Capability is as described by the publisher. | Rule browser-automation matched: “browser”, “automation”. Rule browser-automation. |
Published pricing
No published price recordedCost 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://api.webrun.ai/mcp(streamable-http, declares a required credential)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
ai.webrun/webrun
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.