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/ShalomObongo/chrome-bridge-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/shalomobongo/chrome-bridge-mcp/chrome-bridge-mcp)<a href="https://agentmods.dev/mcp/shalomobongo/chrome-bridge-mcp/chrome-bridge-mcp"><img src="https://agentmods.dev/badge/mcp/shalomobongo/chrome-bridge-mcp/chrome-bridge-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/shalomobongo/chrome-bridge-mcp/chrome-bridge-mcp"><img src="https://agentmods.dev/badge/mcp/shalomobongo/chrome-bridge-mcp/chrome-bridge-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chrome-bridge-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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- chrome-bridge-mcp — 100% identical, 0 lines differ
What it actually says
{ "chrome-bridge-mcp": { "command": "npx", "args": [ "-y", "chrome-bridge-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.
- 11d ago First seen · 9 lines scan A 26a117d3ad4f
chrome-bridge-mcp is an MCP server published in the GitHub repository ShalomObongo/chrome-bridge-mcp (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
public-browser
Public Browser MCP Server - Chrome browser automation via CDP. Runs locally from the public-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.
codex-control-chrome-mcp
MCP server and native host bridge for controlling Chrome through the Codex Chrome extension. Runs locally from the codex-control-chrome-mcp npm package.
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.
chromium-bridge
MCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation. Runs locally from the chromium-bridge npm package.