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.
npx agentmods add mcp/linsipeng/hermes-chrome-bridge/agent-browser-mcpgit clone --depth 1 https://github.com/linsipeng/hermes-chrome-bridgeWrote 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/linsipeng/hermes-chrome-bridge/agent-browser-mcp)<a href="https://agentmods.dev/mcp/linsipeng/hermes-chrome-bridge/agent-browser-mcp"><img src="https://agentmods.dev/badge/mcp/linsipeng/hermes-chrome-bridge/agent-browser-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agent-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 5d 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-mcp": { "command": "uvx", "args": [ "agent-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.
- 5d ago First seen · 8 lines scan A 3150535416bc
agent-browser-mcp is an MCP server published in the GitHub repository linsipeng/hermes-chrome-bridge (0 stars, last pushed 1mo 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
browsertap-mcp
Real-browser MCP server with a BrowserBridge/CDP transport, screenshots, cookies, and physical input. Runs locally from the browsertap-mcp Python package. Needs 4 environment variables to run.
crawlio-browser
Bridge a live Chrome browser to your agent: 150 tools for capture, extraction, and observation. Runs locally from the crawlio-browser npm package.
custom-chrome-dev-mcp
MCP server "custom-chrome-dev-mcp" as configured in HabaAndrei/custom-chrome-dev-mcp. Runs locally from the custom-chrome-dev-mcp npm package.
chrome-bridge-mcp
MCP server with 63 tools for browser automation via Chrome extension. Works on ChromeOS/Crostini. Runs locally from the chrome-bridge-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.
browser-mcp
Browser MCP — control your real Chrome from Claude Code. 34 tools, CAPTCHA solving, date pickers, autocomplete combobox, overlay dismissal, file upload, multi-session, human-in-the-loop. Runs locally from the @agent360/browser-mcp npm package.