Remote MCP · Endpoint

WebRun Browser Automation MCP server

No. WebRun Browser Automation answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
107 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 18 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
1 hour agoHandshake completed107 ms
1 day agoHandshake completed68 ms
3 days agoHandshake completed65 ms
3 days agoHandshake completed55 ms
4 days agoHandshake completed68 ms
5 days agoHandshake completed79 ms
7 days agoHandshake completed61 ms
10 days agoHandshake completed53 ms
12 days agoHandshake completed52 ms
14 days agoHandshake completed77 ms
17 days agoHandshake completed67 ms
19 days agoHandshake completed618 ms
21 days agoHandshake completed94 ms
23 days agoHandshake completed98 ms
25 days agoHandshake completed55 ms
26 days agoHandshake completed59 ms
28 days agoHandshake completed156 ms
29 days agoHandshake completed96 ms

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

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.