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/soundbytelabs/sbl-debugger-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/soundbytelabs/sbl-debugger-mcp/debugger)<a href="https://agentmods.dev/mcp/soundbytelabs/sbl-debugger-mcp/debugger"><img src="https://agentmods.dev/badge/mcp/soundbytelabs/sbl-debugger-mcp/debugger/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/soundbytelabs/sbl-debugger-mcp/debugger"><img src="https://agentmods.dev/badge/mcp/soundbytelabs/sbl-debugger-mcp/debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
debugger 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.
What it actually says
{
"debugger": {
"command": "uvx",
"args": [
"sbl-debugger"
],
"env": {}
}
}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 52b227bbbef9
debugger is an MCP server published in the GitHub repository soundbytelabs/sbl-debugger-mcp (0 stars, last pushed 7mo 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-08-31.
Other mcp servers, from other repositories
jlink-mcp
Debug embedded firmware on real hardware: J-Link probes, Cortex-M faults, RTT logs, GDB. Runs locally from the jlink-mcp npm package. Needs 4 environment variables to run.
wlanpi-mcp
MCP server "wlanpi-mcp" as configured in WLAN-Pi/wlanpi-mcp. Runs locally from the wlanpi-mcp Python package.
cisco-cucm-mcp
MCP server for CUCM operational debugging: DIME logs, AXL config, RIS device status, PerfMon counters, service health, packet capture, and pcap analysis. Runs locally from the @calltelemetry/cisco-cucm-mcp npm package.
hardware-logging
MCP server "hardware-logging" as configured in gurul/hardware-logging. Runs locally from the hardware-logging Python package.
mcubuddy
AI-native debugging and observability for embedded boards. Runs locally from the McuBuddy Python package.
boot-doctor-mcp
Real, deterministic MCP server for PC no-boot/no-display troubleshooting -- real beep-code tables and a rule-based diagnostic sequence, no LLM guessing at hardware causes. Runs locally from the boot-doctor-mcp Python package.