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/0xsoftboi/suwappubot/chrome-devtoolsgit clone --depth 1 https://github.com/0xSoftBoi/suwappubotWrote 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/0xsoftboi/suwappubot/chrome-devtools)<a href="https://agentmods.dev/mcp/0xsoftboi/suwappubot/chrome-devtools"><img src="https://agentmods.dev/badge/mcp/0xsoftboi/suwappubot/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 5d 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
83% identical to chrome-devtools — 4 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": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest",
"--headless",
"--isolated"
]
}
}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.
- 5d ago First seen · 11 lines scan A 8499bb8234d2
chrome-devtools is an MCP server published in the GitHub repository 0xSoftBoi/suwappubot (3 stars, last pushed 2d ago), licensed Apache-2.0. 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 83% identical to chrome-devtools, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
mcp
Gasless, MEV-protected onchain token swaps for AI agents on 14 EVM chains, built on CoW Protocol. Remote server at mcp.ophis.fi.
dexpaprika
Real-time DEX and on-chain data: liquidity pools, token prices, swaps, and trading volume. Remote server at mcp.dexpaprika.com.
krait-solodit
MCP server "krait-solodit" as configured in ZealynxSecurity/krait. Runs mcp-servers/solodit/build/index.js with node.
krait-forge
MCP server "krait-forge" as configured in ZealynxSecurity/krait. Runs mcp-servers/forge/build/index.js with node.
perp-cli
Multi-DEX Perpetual Futures CLI - Pacifica, Hyperliquid, Lighter, Aster. Runs locally from the perp-cli npm package.
coingecko-mcp-server
Crypto market data via CoinGecko — prices, markets, history, trending, and deep coin metadata. Runs locally from the @cyanheads/coingecko-mcp-server npm package. Needs 2 environment variables to run.