Debuganything MCP server
io.github.shreyassaw5394/debuganything·v1.0.1·13 starsObserve any running process from your agent. strace, py-spy, perf, lsof, tcpdump as evidence.
13 stars70 downloads/wk
Reviews
Write oneNobody has reviewed Debuganything yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Debuganything tools (2)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
dea_port_busy"address already in use": find the process holding a port.
portthe TCP/UDP port that is busy
Public scan report
scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it
- Code scan28 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Debuganything compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 90% of 4,460 AI and agents servers
- Tools
- 2
- the typical AI and agents server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 13
- more than 86% of 2,711 AI and agents servers
- Downloads a week
- 70
- more than 54% of 1,538 AI and agents servers with a package
What its tools let an agent do: 2 read
Install Debuganything in Claude Code, Cursor or VS Code
Runs npx -y debuganything on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add debuganything -- npx -y debuganything
What the publisher says
From the Debuganything repository's README, as published. We do not edit it. Read it on GitHub
Debug Anything
Observe any running process. No breakpoints, no restarts, no instrumentation.
One MCP server and CLI that gives any coding agent — Claude Code, Codex, Cursor, Gemini CLI — eyes on running software: syscalls, CPU flamegraphs, thread stacks, sockets and file descriptors, packets, heap retainers, container state. Battle-tested local tools (strace, py-spy, perf, lsof, tcpdump, gdb/lldb, Node's inspector) do the observing; Debug Anything turns their output into structured evidence an agent can reason about and a human can audit.
Quick start · How Debug Anything works · What you can observe · Showcases · Workflows · Python / LangChain / CrewAI · Safety · FAQ · Roadmap · Community
npx debuganything why <pid> # or: why api-container --symptom leakOne command against any pid, container or pod: attach → the right tools for the symptom (slow / leak / hang / crash / triage) → ranked findings, every one citing evidence ids → detach. Hooking it to your agent instead: npx debuganything setup. No install at all? Paste tool output in the browser.
Website: · Community: Discord · Discussions · Only ever download Debug Anything from this repo, the debuganything npm/PyPI packages, or that site.
Where Debug Anything sits
Step-through debuggers over MCP already exist and are good: debugmcp/mcp-debugger (7 languages), microsoft/DebugMCP (VS Code), jdwp-mcp (Java), jkolo/debug-mcp (.NET), pprof-mcp-agent (Go). They need a debug adapter, a debug port, or an instrumented/restarted target, and they assume you already know where to put the breakpoint.
Debug Anything is the layer before that: black-box observation of any pid, container or pod with zero instrumentation, turned into evidence.
mcp-debugger is for when you know where to put the breakpoint. Debug Anything is for when you don't.
They are complementary. When Debug Anything localizes a problem to a function or thread, its suggestednext includes the handoff: "attach a step debugger (e.g. mcp-debugger) at file:function" — and, for native symbols, "decompile parseframe in libfoo.so with your static-analysis tool". More situations: docs/examples.md.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Debuganything: common questions
- Is Debuganything MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Debuganything safety report
- How do I install Debuganything?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Debuganything need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Debuganything maintained?
- The last commit was 8 days ago (2026-10-27). The latest release is v1.0.1.
- What can I use instead of Debuganything?
- Servers from other publishers that do the same job: HOL Guard MCP server, Watch Skill MCP server and OpenWorkProof MCP server.
- How does Debuganything compare with other AI and agents MCP servers?
- safety score 92/100 (higher than 90% of 4,460 AI and agents servers); tools 2 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Debuganything
Same job from other publishers: the closest match first, then the best rated.
- HOL GuardLocal-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.not reviewedEstablishedA
- Watch SkillWatch video and live sessions, keep timestamped evidence, and verify an agent's own work.not reviewedEstablishedB
- OpenWorkProofVerifiable agent evidence; opt-in Codex guard and reference SOC alert review.not reviewedEstablishedA
- SuperlogOpen-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.not reviewedEstablishedA
- AttestixAI agent identity, signed credentials, delegated authority and governance evidence.not reviewedEstablishedA
