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/pleasedodisturb/web-agent-comparison/chrome-devtoolsgit clone --depth 1 https://github.com/pleasedodisturb/web-agent-comparisonWrote 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.svg" alt="Measured on agentmods" 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 3d 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.
- 3d 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 22d 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
browser-use
Make websites accessible for AI agents. Runs locally from the browser-use Python package.
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 2 environment variables to run.
ai-browser
MCP server "ai-browser" as configured in AI-XiaoDao/ai-browser-mcp. Runs CEFbro/AI-Fbowser-Mcp/mcp_bridge.js with node. Needs 3 environment variables to run.
openbrowser-ai
Agentic browser automation using LangGraph and raw CDP. Runs locally from the openbrowser-ai Python package. Needs 7 environment variables to run.
tidesurf
MCP server "tidesurf" as configured in TideSurf/core. Launched with bun src/cli.ts mcp.
aginxbrowser
Stealth web browser for agents: search, fetch, click, download and type in persistent MCP sessions. Remote server at browser.aginx.net.