Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ywleeo/browser-mcpWrote 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/ywleeo/browser-mcp/ai-browser-mcp)<a href="https://agentmods.dev/mcp/ywleeo/browser-mcp/ai-browser-mcp"><img src="https://agentmods.dev/badge/mcp/ywleeo/browser-mcp/ai-browser-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/ywleeo/browser-mcp/ai-browser-mcp"><img src="https://agentmods.dev/badge/mcp/ywleeo/browser-mcp/ai-browser-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ai-browser-mcp 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 8d 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
{ "ai-browser-mcp": { "command": "uvx", "args": [ "ai-browser-mcp" ] } }
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.
- 8d ago First seen · 8 lines scan A fe4396b4a6ea
ai-browser-mcp is an MCP server published in the GitHub repository ywleeo/browser-mcp (6 stars, last pushed 8d 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-31.
Other mcp servers, from other repositories
dsh-web-search-free
A locally run web-search provider that can be connected to coding agents such as Claude Code and Codex. It supports a free search option, a paid search option, and two ways for software to connect to it.
chrome-faithful
MCP server "chrome-faithful" as configured in bpc-oss/chrome-faithful. Runs src/mcp-server.mjs with node. Needs 1 environment variable to run.
dsh-verify
Agent-built web app quality gate. Real browser is the judge. PASS/FAIL with receipts. Runs locally from the dsh-verify npm package.
web-bridge-mcp
MCP Server: AI editors call tools over stdio/HTTP to eval JS, read the console, and simulate input on any static web page that includes client.js. Runs locally from the web-bridge-mcp npm package.
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.
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.