Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Saik0s/mcp-browser-use/plugin install mcp-browser-useWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/saik0s/mcp-browser-use/browser-use)<a href="https://agentmods.dev/mcp/saik0s/mcp-browser-use/browser-use"><img src="https://agentmods.dev/badge/mcp/saik0s/mcp-browser-use/browser-use.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
browser-use scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"browser-use": {
"type": "stdio",
"command": "python3",
"args": [
"${CLAUDE_PLUGIN_ROOT}/scripts/mcp-server.py"
],
"env": {
"PYTHONPATH": "${CLAUDE_PLUGIN_ROOT}/src"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 12 lines scan A 588daaa72859
browser-use is an MCP server published in the GitHub repository Saik0s/mcp-browser-use (958 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 2 environment variables to run.
camoufox-research
MCP server for browser research on the anti-detect Camoufox browser: search, page reading (incl. JS/SPA), batch fetch, clicks, typing, sessions, cache. Runs locally from the camoufox-research Python package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
mare-browser-mcp
Lean, LLM-first browser automation MCP server. Gives Claude, OpenCode, or any MCP client a real browser to navigate, interact with, and debug web apps. Runs locally from the mare-browser-mcp npm package.
crawlgraph-mcp
MCP server "crawlgraph-mcp" as configured in pucilpet/crawlgraph-mcp. Launched with https://github.com/pucilpet/crawlgraph-mcp/releases/download/v0.2.2/crawlgraph-m. Needs 1 environment variable to run.