Back to MCP servers

com.browser-use/browser-use

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

● healthy

Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.

Transport

streamable-http

Auth

required_headers

Cost

—

Protocol revision

2024-11-05

negotiated, not declared

MCP readiness

B · 84/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here A, 97.6/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (208 ms).
Protocol revision	5/10	Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	22/22 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 7 tool(s) with descriptions.
Verified identity	7/10	Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags	2/5	seen within 30 days.
Auth declaration	2/5	Declares credential scheme: required_headers.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (208 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-10.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 52,570 reachable MCP servers in our daily snapshot (2026-11-11 14:47 UTC). Display only; it does not change search order.

Readiness: Higher than 75% of peers; This listing 84 · peer median 81
Latency: Faster than 78% of peers; This listing 169 ms · peer median 371 ms

Where it loses the most points

Protocol revision −5 — Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28.
Verified identity −3 — Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags −3 — seen within 30 days.

How many agent tools actually work · All statistics

Adoption signals

Public signals from outside this directory, shown for context. They do not change search order or grades.

GitHub: ★ 120,690 · 13,491 forks; last push 2026-11-11
Site rank (Tranco): #70,909 of the top 1M; browser-use.com · list of 2026-11-10

Listed in

Directories this entry was found in.

mcp-registry since 2026-10-21 capkey since 2026-10-26 ↗

How to connect

MCP endpoint (streamable-http)

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

JSON-RPC initialize probe

curl -X POST https://api.browser-use.com/v3/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://browser-use.com

Source code

https://github.com/browser-use/browser-use