# io.github.shreyassaw5394/debuganything (npm · debuganything)

Observe any running process from your agent. strace, py-spy, perf, lsof, tcpdump as evidence.

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- npm · `debuganything`: 83/100 (this document), [markdown](https://verifymcp.io/servers/shreyassaw5394-debuganything/debuganything.md), [page](https://verifymcp.io/servers/shreyassaw5394-debuganything/debuganything)

## Channel facts

- Registry: `npm`
- Package: `debuganything`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 42 of 112 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to shreyassaw5394/debuganything).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1390 tokens (~92/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add shreyassaw5394-debuganything -- npx -y debuganything
```

### Cursor

```json
{
  "mcpServers": {
    "shreyassaw5394-debuganything": {
      "command": "npx",
      "args": [
        "-y",
        "debuganything"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shreyassaw5394-debuganything": {
      "command": "npx",
      "args": [
        "-y",
        "debuganything"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add shreyassaw5394-debuganything -- npx -y debuganything
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shreyassaw5394-debuganything": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "debuganything"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shreyassaw5394-debuganything --command npx --arg -y --arg debuganything
```

### Hermes

```yaml
mcp_servers:
  shreyassaw5394-debuganything:
    command: "npx"
    args: ["-y", "debuganything"]
```

### Netclaw

```json
{
  "McpServers": {
    "shreyassaw5394-debuganything": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "debuganything"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add shreyassaw5394-debuganything -t stdio -c npx -a -y debuganything
```

### Other

```json
{
  "mcpServers": {
    "shreyassaw5394-debuganything": {
      "command": "npx",
      "args": [
        "-y",
        "debuganything"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 83, +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.

### 2026-10-22 (score 82, +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.

### 2026-10-20 (score 81, +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.

### 2026-10-19 (score 80)

First indexed and scored.

## MCP tools (15)

### `readiness` (~66 tokens)

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.

### `attach` (~101 tokens)

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.

Input parameters:

- `kind` (string): Defaults to auto-detect: numeric → pid, else container, else command
- `target` (string, required): pid, container name/id, k8s pod (ns/name), or a command line (with kind=command)

### `detach` (~39 tokens)

Stop any running captures for the session, finalize the report, keep artifacts under ~/.debuganything/sessions/<id>/.

Input parameters:

- `session_id` (string, required)

### `list_processes` (~57 tokens)

ps-style list (pid, comm, cpu, mem, user, container) for picking a target. Optional substring filter.

Input parameters:

- `filter` (string): Substring match on command / args / user
- `limit` (integer)

### `trace_syscalls` (~80 tokens)

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.

Input parameters:

- `categories` (array)
- `duration_s` (integer)
- `session_id` (string, required)

### `profile_cpu` (~72 tokens)

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.

Input parameters:

- `consent` (boolean)
- `duration_s` (integer)
- `session_id` (string, required)

### `dump_stacks` (~56 tokens)

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.

Input parameters:

- `session_id` (string, required)

### `inspect_sockets` (~53 tokens)

lsof/ss view of the target: listening ports, established connections grouped by remote, states (CLOSE_WAIT pileups, TIME_WAIT counts), fd count vs ulimit.

Input parameters:

- `session_id` (string, required)

### `inspect_files` (~63 tokens)

Open file descriptors by type, growth over a short window, largest open files, deleted-but-open files (disk full but nothing there).

Input parameters:

- `session_id` (string, required)
- `window_s` (integer): Observe fd growth over this many seconds (0 = single snapshot)

### `capture_traffic` (~117 tokens)

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.

Input parameters:

- `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, required)

### `snapshot_memory` (~92 tokens)

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.

Input parameters:

- `heap` (boolean): Take a heap snapshot where supported (Node). Set false for metrics only.
- `session_id` (string, required)
- `window_s` (integer): Sample RSS over this many seconds

### `diff_runs` (~116 tokens)

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.

Input parameters:

- `a` (string, required): run id of the earlier result; '<session_id>:<run>' reads a baseline run from another session (e.g. a recorded healthy run)
- `b` (string, required): run id of the later result; '<session_id>:<run>' works here too
- `session_id` (string, required)

### `container_info` (~49 tokens)

docker inspect/stats/top/logs tail for the target container, host pid mapping, cgroup limits: throttled? OOM-killed before? restarts?

Input parameters:

- `session_id` (string, required)

### `report` (~79 tokens)

Markdown report of the whole session: findings, evidence excerpts, artifact paths. Optionally written to a file.

Input parameters:

- `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, required)

### `import_artifact` (~151 tokens)

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).

Input parameters:

- `duration_s` (integer): How long the capture ran, when the file has no timestamps (profiles)
- `path` (string, required): Path to the raw output file you captured yourself (e.g. with sudo)
- `session_id` (string, required)
- `tool` (string, required): What produced the file

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/shreyassaw5394-debuganything/debuganything#diagnostics

## Score history

- 2026-10-25: 83
- 2026-10-24: 83
- 2026-10-23: 82
- 2026-10-22: 82
- 2026-10-21: 81
- 2026-10-20: 81
- 2026-10-19: 80

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/debuganything
- Socket report: https://socket.dev/npm/package/debuganything
- Repository: https://github.com/shreyassaw5394/debuganything
- Website: https://debuganything.dev/
- Changelog RSS feed: https://verifymcp.io/servers/shreyassaw5394-debuganything/debuganything.xml
- Changelog JSON feed: https://verifymcp.io/servers/shreyassaw5394-debuganything/debuganything.json
- HTML version of this page: https://verifymcp.io/servers/shreyassaw5394-debuganything/debuganything