Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add lordamdal/chromeboost/plugin install chromeboostWrote 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/lordamdal/chromeboost/plugin-chromeboost)<a href="https://agentmods.dev/mcp/lordamdal/chromeboost/plugin-chromeboost"><img src="https://agentmods.dev/badge/mcp/lordamdal/chromeboost/plugin-chromeboost.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
chromeboost 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 4d 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
{
"chromeboost": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/server/chromeboost.mjs"
]
}
}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.
- 4d ago First seen · 8 lines scan A 48b5830e2ead
chromeboost is an MCP server published in the GitHub repository lordamdal/chromeboost (7 stars, last pushed 5d 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
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.
tap
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay. Runs locally from the @taprun/cli npm package.
sidebutton
Open-source MCP server with browser automation and knowledge packs for AI agents. Runs locally from the @sidebutton/server npm package.
yad-agent-mcp
MCP wrapper for Yad, a local browser-automation companion, for coding agents. Runs locally from the yad-agent-mcp npm package. Needs 1 environment variable to run.