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/MadAppGang/dingoWrote 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/madappgang/dingo/chrome-devtools)<a href="https://agentmods.dev/mcp/madappgang/dingo/chrome-devtools"><img src="https://agentmods.dev/badge/mcp/madappgang/dingo/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/madappgang/dingo/chrome-devtools"><img src="https://agentmods.dev/badge/mcp/madappgang/dingo/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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 9 lines scan A 4f096813cf17
chrome-devtools is an MCP server published in the GitHub repository MadAppGang/dingo (1,915 stars, last pushed 1mo ago), with no licence file. 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-08-30.
Other mcp servers, from other repositories
gograph
MCP server "gograph" as configured in ozgurcd/gograph. Launched with https://github.com/ozgurcd/gograph/releases/download/v1.7.4/gograph_1.7.4_darwin.
project-graph-mcp
MCP server for AI agents — project graph, code quality analysis, visual web explorer. JS, TS, Python, Go. Runs locally from the project-graph-mcp npm package.
compiler-explorer
Compile code with thousands of compilers, inspect the assembly, and share godbolt.org links. Remote server at godbolt.org.
lsp
MCP server "lsp" as configured in blackwell-systems/agent-lsp. Launched with agent-lsp go:gopls.
web-researcher
MCP server "web-researcher" as configured in zoharbabin/web-researcher-mcp. Launched with web-researcher-mcp. Needs 59 environment variables to run.
web-researcher-mcp
MCP server "web-researcher-mcp" as configured in zoharbabin/web-researcher-mcp. Runs in Docker (ghcr.io/zoharbabin/web-researcher-mcp:1.9.0). Needs 8 environment variables to run.