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/nextster/chromium-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/nextster/chromium-bridge/chromium-bridge-chromium-bridge)<a href="https://agentmods.dev/mcp/nextster/chromium-bridge/chromium-bridge-chromium-bridge"><img src="https://agentmods.dev/badge/mcp/nextster/chromium-bridge/chromium-bridge-chromium-bridge/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/nextster/chromium-bridge/chromium-bridge-chromium-bridge"><img src="https://agentmods.dev/badge/mcp/nextster/chromium-bridge/chromium-bridge-chromium-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chromium-bridge 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
{
"chromium-bridge": {
"command": "node",
"args": [
"./mcp/server.mjs"
],
"cwd": "."
}
}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 · 9 lines scan A 82055695a410
chromium-bridge is an MCP server published in the GitHub repository nextster/chromium-bridge (0 stars, last pushed 9d 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
ghostlight
Visible local browser automation in signed-in Chromium, with optional policy and audit. Runs locally from the ghostlight npm package.
cloakbrowser-mcp
Playwright MCP-compatible browser automation bridge for CloakBrowser Chromium. Runs locally from the cloakbrowser-mcp npm package. Needs 10 environment variables to run.
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.
browser-mcp
MCP server "browser-mcp" as configured in EndymionLee/PilotBrowseMCP. Runs BrowserPlugin\server\dist\index.js with node.
drisp-browser-dev
MCP server "drisp-browser-dev" as configured in drisplabs/browser-mcp. Runs dist/src/index.js with node.