io.github.shreyassaw5394/debuganything
NPM · DEBUGANYTHING
Observe any running process from your agent. strace, py-spy, perf, lsof, tcpdump as evidence.
Available components
Last scanned (7 hours ago)
Scores higher than 79% of npm servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 42 of 112 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to shreyassaw5394/debuganything). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1390 tokens (~92/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 80
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Analysed npm/debuganything@1.0.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | shreyassaw5394/debuganything |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/shreyassaw5394/debuganything/.github/workflows/publish-npm.yml@refs/tags/v1.0.1 |
| Rekor log index | 3319864444 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:07adf366771add26dc4493f638725a6c81aa0a9ec869bf6db759f86eeed9a6bd99f8715743864a843d54f5b1227b12cd1024032ac381f4f91295a82b3 |
Background: How many MCP packages publish verified provenance →
Dependencies 112 packages
| Packages resolved | 112 |
|---|---|
| Stale | 42 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
attach ~101
Resolve a target (pid, container, k8s pod, or a command to spawn under capture) and open a session. Returns session_id used by every other tool. Read-only: nothing is modified.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Defaults to auto-detect: numeric → pid, else container, else command |
| target | string | yes | pid, container name/id, k8s pod (ns/name), or a command line (with kind=command) |
No output schema declared.
No examples provided.
capture_traffic ~117
tcpdump scoped to the target's ports for N seconds (max 30). Per-remote bytes/packets, retransmits, RSTs, DNS queries, TLS SNI. .pcap artifact. REQUIRES consent: true — ask the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| consent | boolean | – | Required. Packet capture may contain secrets; ask the user first. |
| duration_s | integer | – | – |
| filter | string | – | Extra BPF filter ANDed with the target's ports |
| session_id | string | yes | – |
No output schema declared.
No examples provided.
container_info ~49
docker inspect/stats/top/logs tail for the target container, host pid mapping, cgroup limits: throttled? OOM-killed before? restarts?
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
detach ~39
Stop any running captures for the session, finalize the report, keep artifacts under ~/.debuganything/sessions/<id>/.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
diff_runs ~116
Diff two prior runs of the same tool in this session (e.g. snapshot_memory#1 vs snapshot_memory#2, profile_cpu#1 vs #2): what grew, appeared, disappeared.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | run id of the earlier result; '<session_id>:<run>' reads a baseline run from another session (e.g. a recorded healthy run) |
| b | string | yes | run id of the later result; '<session_id>:<run>' works here too |
| session_id | string | yes | – |
No output schema declared.
No examples provided.
dump_stacks ~56
Instant snapshot of every thread's stack (py-spy dump / gdb / lldb / Node inspector). The key tool for hangs and deadlocks; flags threads waiting on the same lock.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
import_artifact ~151
Analyze raw tool output you captured yourself (e.g. `sudo strace …`, `sudo fs_usage …`, `perf script`, `py-spy dump`, `lsof -F`, `tcpdump -nn -tt -r`) and turn it into the same evidence and findings Debug Anything would produce. Use when Debug Anything could not run the tool (no root, macOS).
| Name | Type | Req | Description |
|---|---|---|---|
| duration_s | integer | – | How long the capture ran, when the file has no timestamps (profiles) |
| path | string | yes | Path to the raw output file you captured yourself (e.g. with sudo) |
| session_id | string | yes | – |
| tool | string | yes | What produced the file |
No output schema declared.
No examples provided.
inspect_files ~63
Open file descriptors by type, growth over a short window, largest open files, deleted-but-open files (disk full but nothing there).
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| window_s | integer | – | Observe fd growth over this many seconds (0 = single snapshot) |
No output schema declared.
No examples provided.
inspect_sockets ~53
lsof/ss view of the target: listening ports, established connections grouped by remote, states (CLOSE_WAIT pileups, TIME_WAIT counts), fd count vs ulimit.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
list_processes ~57
ps-style list (pid, comm, cpu, mem, user, container) for picking a target. Optional substring filter.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Substring match on command / args / user |
| limit | integer | – | – |
No output schema declared.
No examples provided.
profile_cpu ~72
CPU profile for N seconds: py-spy (Python), perf (native/Node on Linux), sample (macOS). Returns top frames (self/total), hottest stacks, flamegraph.svg artifact.
| Name | Type | Req | Description |
|---|---|---|---|
| consent | boolean | – | – |
| duration_s | integer | – | – |
| session_id | string | yes | – |
No output schema declared.
No examples provided.
readiness ~66
Report OS, arch, which providers (strace, py-spy, perf, lsof, tcpdump, gdb/lldb, docker...) are usable, what is missing and how to install it, and permission status (ptrace_scope, sudo, SIP). Always call this first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
report ~79
Markdown report of the whole session: findings, evidence excerpts, artifact paths. Optionally written to a file.
| Name | Type | Req | Description |
|---|---|---|---|
| html | boolean | – | Also render a self-contained report.html (shareable: ranked findings, expandable evidence, embedded flamegraphs) |
| out | string | – | Optional path to also write the markdown to |
| session_id | string | yes | – |
No output schema declared.
No examples provided.
snapshot_memory ~92
RSS/VSZ sampled over a window; Node: heap snapshot with top retainers by retained size; Python: py-spy dump with locals. Take two and diff_runs them to find what grows.
| Name | Type | Req | Description |
|---|---|---|---|
| heap | boolean | – | Take a heap snapshot where supported (Node). Set false for metrics only. |
| session_id | string | yes | – |
| window_s | integer | – | Sample RSS over this many seconds |
No output schema declared.
No examples provided.
trace_syscalls ~80
Linux strace of the target for N seconds: top syscalls by total time and count, slowest individual calls, error counts (ENOENT/EAGAIN/ECONNREFUSED...), blocked waits. Raw log saved as artifact.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | – |
| duration_s | integer | – | – |
| session_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.shreyassaw5394/debuganything MCP server?
io.github.shreyassaw5394/debuganything runs locally as an npm package, launched with npx -y debuganything. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · debuganything
claude mcp add shreyassaw5394-debuganything -- npx -y debuganything
What is the io.github.shreyassaw5394/debuganything MCP server?
io.github.shreyassaw5394/debuganything is an MCP server listed in the public MCP registry as io.github.shreyassaw5394/debuganything. Observe any running process from your agent. strace, py-spy, perf, lsof, tcpdump as evidence. This page covers its npm package (debuganything).
Is the io.github.shreyassaw5394/debuganything MCP server safe to use?
io.github.shreyassaw5394/debuganything scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.shreyassaw5394/debuganything MCP server expose?
io.github.shreyassaw5394/debuganything exposes 15 tools: readiness, attach, detach, list_processes, trace_syscalls, and 10 more. Their descriptions and schemas cost roughly 1,191 tokens of context every time the server is loaded.
Is the io.github.shreyassaw5394/debuganything MCP server still maintained?
io.github.shreyassaw5394/debuganything is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.shreyassaw5394/debuganything MCP server under?
io.github.shreyassaw5394/debuganything declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.