com.browser-use/browser-use
REMOTE · API.BROWSER-USE.COM · 2 COMPONENTS
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
Available components
Last scanned (6 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Browser Automation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 826 tokens (~118/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_task" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://api.browser-use.com/v3/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.browser-use.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 28 Aug 2026 | 13 Mar 2027 | RSA 2048 | SHA256-RSA | d6396b085c2de887c9ae6ff561ab235 |
| SANs: api.browser-use.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.browser-use.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| browser-use.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="MCP v3 Server", resource_metadata_uri="https://api.browser-use.com/.well-known/oauth-protected-resource"
Bearer realm="MCP v3 Server", resource_metadata_uri="https://api.browser-use.com/.well-known/oauth-protected-resource"Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.browser-use.com/v3/mcp | Verified | 200 | |
| http (plaintext) | http://api.browser-use.com/v3/mcp | HTTPS enforced | 301 | https://api.browser-use.com:443/v3/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_session ~68
Get current status and output of a session. Call this repeatedly to poll for task completion. Returns status (created, idle, running, stopped, timed_out, error), step count, output, cost breakdown, and live URL.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | UUID of the session to check. |
No output schema declared.
No examples provided.
get_session_messages ~97
Get the agent messages/steps for a session. Shows what the agent is doing including browser actions, reasoning, and results. Use after= parameter for pagination to get new messages since your last check.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Return messages after this message ID (cursor-based pagination). Omit for initial fetch. |
| limit | integer | – | Max number of messages to return. |
| session_id | string | yes | UUID of the session. |
No output schema declared.
No examples provided.
list_browser_profiles ~62
List all available cloud browser profiles for the authenticated project. Profiles store persistent authentication (cookies, sessions) for websites requiring login. Use this BEFORE attempting any authenticated tasks. Show profiles to the user and let them choose, then pass the selected profile_id to run_session.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sessions ~46
List recent sessions for the authenticated project, with status and cost info.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-indexed). |
| page_size | integer | – | Results per page. |
No output schema declared.
No examples provided.
run_session ~355
Create a new browser agent session and run a task. This uses the v3 sandbox-based agent that supports long-running sessions, workspaces, and keep-alive. After creating a session, call get_session to poll for status and output. For tasks requiring authentication, use list_browser_profiles first to get a profile_id.
| Name | Type | Req | Description |
|---|---|---|---|
| keep_alive | boolean | – | If true, the session stays idle after the task finishes, ready for follow-up tasks via send_task. Default is false (session auto-stops). |
| model | string | – | Agent model to use. When omitted, an account-appropriate default is selected. Available: gemini-3-flash, claude-sonnet-5, claude-opus-4.6, claude-opus-4.7, claude-opus-4.8, gpt-5.4-mini, glm-5.2, min… |
| output_schema | object | – | JSON schema for structured output. The agent will return data matching this schema. |
| profile_id | string | – | UUID of the cloud profile to use for authenticated tasks. Get this from list_browser_profiles. |
| proxy_country | – | – | ISO 3166-1 alpha-2 country code for the proxy location (e.g. "us", "gb", "de", "jp", "br"). Defaults to "us" if not specified. Set to null to disable the proxy. |
| task | string | yes | Detailed instructions for what you want the browser agent to do. |
| workspace_id | string | – | UUID of the workspace for file persistence across sessions. |
No output schema declared.
No examples provided.
send_task ~114
Send a follow-up task to an existing keep-alive session. The session must be in idle status. Use this for multi-turn interactions where you want to reuse the same browser context.
| Name | Type | Req | Description |
|---|---|---|---|
| keep_alive | boolean | – | If true, session stays idle after this task too. Default is false. |
| output_schema | object | – | JSON schema for structured output. |
| session_id | string | yes | UUID of an existing idle session (from run_session with keep_alive=true). |
| task | string | yes | The follow-up task instructions. |
No output schema declared.
No examples provided.
stop_session ~84
Stop a running session. Use strategy "task" to stop only the current task (session stays idle for follow-ups), or "session" (default) to destroy the sandbox entirely.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | UUID of the session to stop. |
| strategy | string | – | Stop strategy: "task" stops the current task only, "session" destroys the sandbox. |
No output schema declared.
No examples provided.
How do I install the com.browser-use/browser-use MCP server?
com.browser-use/browser-use is a hosted endpoint at https://api.browser-use.com/v3/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.browser-use.com
claude mcp add --transport http com-browser-use-browser-use 'https://api.browser-use.com/v3/mcp'
What is the com.browser-use/browser-use MCP server?
com.browser-use/browser-use is an MCP server listed in the public MCP registry as com.browser-use/browser-use. Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data. This page covers its hosted endpoint (https://api.browser-use.com/v3/mcp).
Is the com.browser-use/browser-use MCP server safe to use?
com.browser-use/browser-use scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.browser-use/browser-use MCP server expose?
com.browser-use/browser-use exposes 7 tools: run_session, send_task, get_session, get_session_messages, stop_session, and 2 more. Their descriptions and schemas cost roughly 826 tokens of context every time the server is loaded.
Does the com.browser-use/browser-use MCP server require authentication?
Yes. com.browser-use/browser-use asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the com.browser-use/browser-use MCP server still maintained?
com.browser-use/browser-use is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.