Remote MCP · Endpoint

com.browser-use/browser-use MCP server

No. com.browser-use/browser-use answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://api.browser-use.com/v3/mcp

The last check completed an MCP handshake.

Registry name
com.browser-use/browser-use
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
84 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
Listing
From the official MCP registry (active).
Recent checks of com.browser-use/browser-use
CheckedResultHandshake
9 hours agoHandshake completed84 ms
4 days agoHandshake completed68 ms
14 days agoHandshake completed92 ms
15 days agoHandshake completed96 ms
15 days agoHandshake completed94 ms
17 days agoHandshake completed95 ms
18 days agoHandshake completed88 ms
19 days agoHandshake completed104 ms
20 days agoHandshake completed86 ms
21 days agoHandshake completed101 ms
23 days agoHandshake completed103 ms
26 days agoHandshake completed90 ms
28 days agoHandshake completed106 ms

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with com.browser-use/browser-use and makes no claim about it beyond what these checks measured.