Remote MCP · Endpoint

WebRun Browser Automation MCP server

No. WebRun Browser Automation answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://api.webrun.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.webrun/webrun
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
94 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.
Website
https://webrun.ai/
Listing
From the official MCP registry (active).
Recent checks of WebRun Browser Automation
CheckedResultHandshake
6 hours agoHandshake completed94 ms
2 days agoHandshake completed98 ms
4 days agoHandshake completed55 ms
5 days agoHandshake completed59 ms
7 days agoHandshake completed156 ms
8 days agoHandshake completed96 ms
9 days agoHandshake completed83 ms
12 days agoHandshake completed79 ms
13 days agoHandshake completed49 ms
15 days agoHandshake completed88 ms
16 days agoHandshake completed46 ms
17 days agoHandshake completed64 ms
18 days agoHandshake completed71 ms
19 days agoHandshake completed62 ms
20 days agoHandshake completed72 ms
21 days agoHandshake completed45 ms
23 days agoHandshake completed261 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with WebRun Browser Automation and makes no claim about it beyond what these checks measured.