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 hamzahamidi/claude-in-chrome-cli/plugin install claude-in-chromeWrote 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/hamzahamidi/claude-in-chrome-cli/claude-in-chrome-chrome-tabs)<a href="https://agentmods.dev/mcp/hamzahamidi/claude-in-chrome-cli/claude-in-chrome-chrome-tabs"><img src="https://agentmods.dev/badge/mcp/hamzahamidi/claude-in-chrome-cli/claude-in-chrome-chrome-tabs/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/hamzahamidi/claude-in-chrome-cli/claude-in-chrome-chrome-tabs"><img src="https://agentmods.dev/badge/mcp/hamzahamidi/claude-in-chrome-cli/claude-in-chrome-chrome-tabs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chrome-tabs 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.
What it actually says
{
"chrome-tabs": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/tabs_mcp.js"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 8 lines scan A 01725429e406
chrome-tabs is an MCP server published in the GitHub repository hamzahamidi/claude-in-chrome-cli (3 stars, last pushed 18d 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.
vibatchium
Patchright stealth + Vibium-style LLM-friendly CLI for agentic browser automation. Runs locally from the vibatchium Python package.
public-browser
Public Browser MCP Server - Chrome browser automation via CDP. Runs locally from the public-browser 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.
acrawl
MCP server "acrawl" as configured in Mingye-Lu/AgenticCrawler. Launched with https://github.com/Mingye-Lu/AgenticCrawler/releases/download/v0.9.1/acrawl-mcp-.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.