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/debugg-ai/debugg-ai-mcpWrote 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/debugg-ai/debugg-ai-mcp/debugg-ai-local)<a href="https://agentmods.dev/mcp/debugg-ai/debugg-ai-mcp/debugg-ai-local"><img src="https://agentmods.dev/badge/mcp/debugg-ai/debugg-ai-mcp/debugg-ai-local/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/debugg-ai/debugg-ai-mcp/debugg-ai-local"><img src="https://agentmods.dev/badge/mcp/debugg-ai/debugg-ai-mcp/debugg-ai-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
debugg-ai-local 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 10d 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.
What it actually says
{
"debugg-ai-local": {
"type": "stdio",
"command": "node",
"args": [
"dist/index.js"
],
"env": {
"DEBUGGAI_API_KEY": "${DEBUGGAI_API_KEY}"
}
}
}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.
- 10d ago First seen · 12 lines scan A 62cbbadd5e85
debugg-ai-local is an MCP server published in the GitHub repository debugg-ai/debugg-ai-mcp (68 stars, last pushed 21d 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. 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
debug-recorder-mcp
MCP server for recording debug sessions — query your debugging history with natural language. Runs locally from the debug-recorder-mcp npm package. Needs 1 environment variable to run.
zapier-dev-mcp
For Zapier integration developers: inspect, lint, and validate zapier-platform-cli projects. Runs locally from the zapier-dev-mcp npm package.
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.
android-mcp-adb
Full Android control from any AI agent via MCP — 7 tools, 90fps viewer, WiFi ADB. Runs locally from the android-mcp-adb Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.