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/pleasedodisturb/web-agent-comparisonInstalling this writes the configuration, not the program: `chrome-devtools-mcp` has to be on your PATH already, or the server will not start.
Wrote 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/pleasedodisturb/web-agent-comparison/chrome-devtools)<a href="https://agentmods.dev/mcp/pleasedodisturb/web-agent-comparison/chrome-devtools"><img src="https://agentmods.dev/badge/mcp/pleasedodisturb/web-agent-comparison/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/pleasedodisturb/web-agent-comparison/chrome-devtools"><img src="https://agentmods.dev/badge/mcp/pleasedodisturb/web-agent-comparison/chrome-devtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 1mo 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.
This is a copy
100% identical to chrome-devtools — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"chrome-devtools": {
"command": "chrome-devtools-mcp",
"args": []
}
}What else .mcp.json configures
This page is one entry in a file that holds 7. 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.
- 1mo ago First seen · 6 lines scan A 230688e7d53f
chrome-devtools is an MCP server published in the GitHub repository pleasedodisturb/web-agent-comparison (2 stars, last pushed 1mo 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. It is 100% identical to chrome-devtools, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
jshookmcp
Search-first MCP server for JavaScript reverse engineering: 735 tools across 36 domains. Runs locally from the @jshookmcp/jshook npm package.
devharness
MCP server that connects AI assistants to Chrome DevTools Protocol for runtime debugging - set breakpoints, inspect variables, monitor network traffic, and automate browser interactions. Runs locally from the devharness npm package.
feedthrough
Debug bridge inside your web app: an agent reads the DOM, console and network. Any browser. Runs locally from the @feedthrough/mcp npm package. Needs 2 environment variables to run.
devtools-lens-mcp
Give your AI agent Chrome DevTools: an MCP server for debugging Chromium applications. Runs locally from the devtools-lens-mcp npm package.
pwa-debug-layer
Debug PWAs in your real browser via MCP: service-worker, cache, installability & framework state. Runs locally from the @aryanduntley/pwa-debug npm package.
safari-devtools-mcp
MCP server for Safari DevTools — browser debugging and automation for AI coding agents. Runs locally from the safari-devtools-mcp npm package.