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/Blackman99/agent-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/blackman99/agent-browser-mcp/plugin-agent-browser)<a href="https://agentmods.dev/mcp/blackman99/agent-browser-mcp/plugin-agent-browser"><img src="https://agentmods.dev/badge/mcp/blackman99/agent-browser-mcp/plugin-agent-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/blackman99/agent-browser-mcp/plugin-agent-browser"><img src="https://agentmods.dev/badge/mcp/blackman99/agent-browser-mcp/plugin-agent-browser.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-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 1mo 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
{
"agent-browser": {
"command": "npx",
"args": [
"-y",
"agent-browser-mcp-codex"
]
}
}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.
- 1mo ago First seen · 9 lines scan A cfa0cd22f929
agent-browser is an MCP server published in the GitHub repository Blackman99/agent-browser-mcp (1 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-31.
Other mcp servers, from other repositories
aginxbrowser
Stealth web browser for agents: search, fetch, click, download and type in persistent MCP sessions. Remote server at browser.aginx.net.
cockroach-browser
Open-source local-first Chromium, Firefox, WebKit, Playwright, and Puppeteer automation for AI agents with semantic page snapshots, model-directed execution, MCP, SDKs, and verifiable evidence. Runs locally from the cockroach-browser npm package. Needs 2 environment variables to run.
browser-use
Make websites accessible for AI agents. Runs locally from the browser-use Python package.
stagehand
MCP server "stagehand" as configured in browserbase/stagehand. Runs ../core/dist/facade/stdio-server.mjs with node.
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.
openbrowser-ai
Agentic browser automation using LangGraph and raw CDP. Runs locally from the openbrowser-ai Python package. Needs 7 environment variables to run.