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/borbiuk/band-playWrote 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/borbiuk/band-play/chrome-devtools)<a href="https://agentmods.dev/mcp/borbiuk/band-play/chrome-devtools"><img src="https://agentmods.dev/badge/mcp/borbiuk/band-play/chrome-devtools/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/borbiuk/band-play/chrome-devtools"><img src="https://agentmods.dev/badge/mcp/borbiuk/band-play/chrome-devtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade 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 yesterday.
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]",
"--categoryExtensions",
"--no-usage-statistics"
]
}
}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.
- yesterday First seen · 11 lines scan A ea47794354da
chrome-devtools is an MCP server published in the GitHub repository borbiuk/band-play (21 stars, last pushed today), 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-10-26.
Other mcp servers, from other repositories
chrome-devtools-mcp
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the @secforge/chrome-devtools-mcp npm package.
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.
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.
peek-mcp
Exposes recorded browser sessions (rrweb DOM, console, network) to AI coding agents, fully local. Runs locally from the @peekdev/mcp npm package.
peek
local-first browser-session forensics + repro for AI coding agents. peek's native messaging host + stdio MCP server — owns /.peek/sessions.db (better-sqlite3) and bridges the browser extension, CLI, and AI tools to one local source of truth. Runs locally from the @peekdev/mcp npm package.
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.