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/duc01226/easyplatform/chrome-devtoolsgit clone --depth 1 https://github.com/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/chrome-devtools)<a href="https://agentmods.dev/mcp/duc01226/easyplatform/chrome-devtools"><img src="https://agentmods.dev/badge/mcp/duc01226/easyplatform/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 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": {
"args": [
"/c",
"npx",
"-y",
"chrome-devtools-mcp@latest"
],
"command": "cmd",
"description": "Chrome browser automation (navigate, click, screenshot, network/console inspection)"
}
}What else .mcp.json configures
This page is one entry in a file that holds 8. 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 · 12 lines scan A fc8d95d7f1d7
chrome-devtools is an MCP server published in the GitHub repository duc01226/EasyPlatform (9 stars, last pushed 15d 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-09-03.
Other mcp servers, from other repositories
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
apify
Apify MCP Server. Runs locally from the @apify/actors-mcp-server npm package. Needs 2 environment variables to run.
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.
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.
openbrowser-ai
Agentic browser automation using LangGraph and raw CDP. Runs locally from the openbrowser-ai Python package. Needs 7 environment variables to run.
fetch
Lets the agent fetch a URL and read its content as markdown. Runs locally from the mcp-server-fetch Python package.