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/AI-XiaoDao/ai-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/ai-xiaodao/ai-browser-mcp/ai-browser)<a href="https://agentmods.dev/mcp/ai-xiaodao/ai-browser-mcp/ai-browser"><img src="https://agentmods.dev/badge/mcp/ai-xiaodao/ai-browser-mcp/ai-browser/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/ai-xiaodao/ai-browser-mcp/ai-browser"><img src="https://agentmods.dev/badge/mcp/ai-xiaodao/ai-browser-mcp/ai-browser.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ai-browser 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 10d 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": {
"command": "node",
"args": [
"CEFbro/AI-Fbowser-Mcp/mcp_bridge.js"
],
"env": {
"AI_BROWSER_MCP_HTTP_POST": "http://127.0.0.1:9222/mcp",
"AI_BROWSER_MCP_HOST": "127.0.0.1",
"AI_BROWSER_MCP_PORT": "9222"
}
}
}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.
- 10d ago First seen · 13 lines scan A a153aec3317b
ai-browser is an MCP server published in the GitHub repository AI-XiaoDao/ai-browser-mcp (48 stars, last pushed 12d 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
safari-mcp
Native Safari browser automation for AI agents — 80 tools, zero Chrome overhead. Runs locally from the safari-mcp npm package.
real-browser
MCP server + Chrome extension for AI browser control with real sessions. Runs locally from the real-browser-mcp npm package.
openbrowser-ai
Agentic browser automation using LangGraph and raw CDP. Runs locally from the openbrowser-ai Python package. Needs 7 environment variables to run.
aginxbrowser
Stealth web browser for agents: search, fetch, click, download and type in persistent MCP sessions. Remote server at browser.aginx.net.
vibe-mcp
Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port. Runs locally from the @vibebrowser/mcp npm package.
vibe
MCP server that drives your real, logged-in Chrome from any MCP client - including agents on a remote machine, with no inbound port open. Runs locally from the @vibebrowser/mcp npm package.