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/stigmavlc/claude-bridge/chrome-devtoolsgit clone --depth 1 https://github.com/Stigmavlc/claude-bridgeGrade A, and why
chrome-devtools 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 2d 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
{
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"[email protected]",
"--headless=true",
"--isolated=true"
]
}
}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.
- 2d ago First seen · 11 lines scan A 0de69e7f7fe0
chrome-devtools is an MCP server published in the GitHub repository Stigmavlc/claude-bridge (2 stars, last pushed 19d 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
wbrowser
MCP server "wbrowser" as configured in w-partners/Wbrowser. Runs locally from the wbrowser npm package.
chrome-faithful
MCP server "chrome-faithful" as configured in bpc-oss/chrome-faithful. Runs src/mcp-server.mjs with node. Needs 1 environment variable to run.
public-browser
Public Browser MCP Server - Chrome browser automation via CDP. Runs locally from the public-browser npm package.
claude-in-chrome
MCP server "claude-in-chrome" as configured in hamzahamidi/claude-in-chrome-cli. Launched with claude --claude-in-chrome-mcp.
chrome-tabs
MCP server "chrome-tabs" as configured in hamzahamidi/claude-in-chrome-cli. Runs ${CLAUDE_PLUGIN_ROOT}/tabs_mcp.js with node.
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.