# io.github.0xmortuex/gdbstub-mcp (pypi · gdbstub-mcp)

Debug kernels through QEMU's gdbstub with no gdb binary - and explain triple faults.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- pypi · `gdbstub-mcp`: 75/100 (this document), [markdown](https://verifymcp.io/servers/0xmortuex-gdbstub-mcp/gdbstub-mcp.md), [page](https://verifymcp.io/servers/0xmortuex-gdbstub-mcp/gdbstub-mcp)

## Channel facts

- Registry: `pypi`
- Package: `gdbstub-mcp`
- Version: `0.1.0`
- 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-17.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 32 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to 0xmortuex/gdbstub-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1532 tokens (~85/item across 18 items; 18 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "debug_disconnect" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.0xmortuex/gdbstub-mcp server?

io.github.0xmortuex/gdbstub-mcp runs locally as a PyPI package, launched with uvx gdbstub-mcp. 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 0xmortuex-gdbstub-mcp -- uvx gdbstub-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "0xmortuex-gdbstub-mcp": {
      "command": "uvx",
      "args": [
        "gdbstub-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "0xmortuex-gdbstub-mcp": {
      "command": "uvx",
      "args": [
        "gdbstub-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add 0xmortuex-gdbstub-mcp -- uvx gdbstub-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "0xmortuex-gdbstub-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "gdbstub-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 0xmortuex-gdbstub-mcp --command uvx --arg gdbstub-mcp
```

### Hermes

```yaml
mcp_servers:
  0xmortuex-gdbstub-mcp:
    command: "uvx"
    args: ["gdbstub-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "0xmortuex-gdbstub-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "gdbstub-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add 0xmortuex-gdbstub-mcp -t stdio -c uvx -a gdbstub-mcp
```

### Other

```json
{
  "mcpServers": {
    "0xmortuex-gdbstub-mcp": {
      "command": "uvx",
      "args": [
        "gdbstub-mcp"
      ]
    }
  }
}
```

## 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-15 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-14 (score 60, +11)

- [security regression] Malware scan: pass → unverified
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Tool coverage: 0
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 0
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-12 (score 49)

First indexed and scored.

## MCP tools (18)

### `debug_connect` (~211 tokens)

Connect to a gdbstub and register the session under `name`.

For QEMU, start it with `-s` (stub on tcp::1234) or `-gdb tcp::PORT`, and
add `-S` to halt the CPU before the first instruction so you can set
breakpoints before anything runs. With qemu-mcp, pass these via
qemu_boot's extra_args, e.g. extra_args="-s -S".
elf is the kernel image with symbols (and ideally DWARF debug info); it
enables symbol names, file:line breakpoints and source locations.
load_bias is added to every ELF address, for images loaded somewhere other
than their link address (0 for a normally linked kernel).
The target stays halted after connecting.

Input parameters:

- `elf`
- `host` (string)
- `load_bias` (integer)
- `name` (string, required)
- `port` (integer)
- `timeout_s` (number)

Output parameters:

- `result` (string)

### `debug_disconnect` (~41 tokens)

Remove breakpoints, detach from the stub so the guest keeps running,
and forget the session. A running target is halted first.

Input parameters:

- `name` (string, required)

Output parameters:

- `result` (string)

### `debug_sessions` (~13 tokens)

List active debug sessions.

Output parameters:

- `result` (string)

### `debug_registers` (~112 tokens)

Read registers. Target must be halted.

registers is a comma-separated list (e.g. "eip,esp,cr2,cr3"); default is
the general set from the stub's `g` packet. all=True also reads every
extra register the target describes (control registers, segment bases,
FPU/SSE...). Flag registers (eflags, cr0, cr4...) are decoded.

Input parameters:

- `all` (boolean)
- `name` (string, required)
- `registers`

Output parameters:

- `result` (string)

### `debug_set_register` (~48 tokens)

Write a register. value is an address expression (0x10, symbol, ...).

Input parameters:

- `name` (string, required)
- `register` (string, required)
- `value` (string, required)

Output parameters:

- `result` (string)

### `debug_memory` (~121 tokens)

Read guest memory (virtual addresses, as the CPU currently sees them).

address accepts 0x1234, symbol, symbol+0x10, file.c:42 or $esp+8.
format: "hex" (hexdump with ASCII), "words" (pointer-sized words,
symbolized), or "string" (NUL-terminated string at address).
length is capped at 4096 bytes.

Input parameters:

- `address` (string, required)
- `format` (string)
- `length` (integer)
- `name` (string, required)

Output parameters:

- `result` (string)

### `debug_write_memory` (~51 tokens)

Write raw bytes (hex string, e.g. "90 90 cc") to guest memory.

Input parameters:

- `address` (string, required)
- `hex_bytes` (string, required)
- `name` (string, required)

Output parameters:

- `result` (string)

### `debug_break` (~117 tokens)

Set a breakpoint or watchpoint.

location: 0x1234, symbol, symbol+0x10, or file.c:42.
kind: "sw" (software breakpoint), "hw" (hardware breakpoint - use this
before paging is enabled or for code that isn't loaded yet), or a
watchpoint: "write", "read", "access" (length bytes, default one word).

Input parameters:

- `kind` (string)
- `length`
- `location` (string, required)
- `name` (string, required)

Output parameters:

- `result` (string)

### `debug_delete` (~32 tokens)

Remove a breakpoint/watchpoint by its # id.

Input parameters:

- `id` (integer, required)
- `name` (string, required)

Output parameters:

- `result` (string)

### `debug_breakpoints` (~23 tokens)

List breakpoints and watchpoints.

Input parameters:

- `name` (string, required)

Output parameters:

- `result` (string)

### `debug_continue` (~65 tokens)

Resume the target and wait up to timeout_s for it to stop.

If it hasn't stopped by then it keeps running: call debug_wait to keep
waiting, or debug_interrupt to halt it where it is.

Input parameters:

- `name` (string, required)
- `timeout_s` (number)

Output parameters:

- `result` (string)

### `debug_wait` (~37 tokens)

Wait for a running target to stop (after debug_continue timed out).

Input parameters:

- `name` (string, required)
- `timeout_s` (number)

Output parameters:

- `result` (string)

### `debug_interrupt` (~28 tokens)

Halt a running target immediately (like Ctrl-C in gdb).

Input parameters:

- `name` (string, required)

Output parameters:

- `result` (string)

### `debug_step` (~41 tokens)

Single-step `count` machine instructions (1..1000) and show where it stopped.

Input parameters:

- `count` (integer)
- `name` (string, required)

Output parameters:

- `result` (string)

### `debug_backtrace` (~123 tokens)

Show the call stack.

mode "fp" walks the frame-pointer chain (exact, but only if the kernel
was built with frame pointers, e.g. -fno-omit-frame-pointer); "scan"
scans the stack for return addresses (works on -O2 kernels without frame
pointers, x86 only, needs elf; may include stale frames); "auto" tries
fp and falls back to scan if the chain is empty.

Input parameters:

- `max_frames` (integer)
- `mode` (string)
- `name` (string, required)

Output parameters:

- `result` (string)

### `debug_disassemble` (~84 tokens)

Disassemble `count` instructions from address (default: current pc).

bits overrides the decode mode on x86 (16 for real mode, 32, 64) -
useful in bootloader code that runs before the CPU mode matches the ELF.

Input parameters:

- `address`
- `bits`
- `count` (integer)
- `name` (string, required)

Output parameters:

- `result` (string)

### `debug_symbol` (~93 tokens)

Look up symbols without touching the target.

query: an address (0x100abc) -> symbol+offset and source line; a symbol or
symbol+off -> its address, size and source line; or file.c:42 -> address.
Uses the session's ELF (name=) or a standalone ELF path (elf=).

Input parameters:

- `elf`
- `name`
- `query` (string, required)

Output parameters:

- `result` (string)

### `debug_explain_fault` (~132 tokens)

Explain a crash / triple fault from a QEMU interrupt log.

Produce the log by running QEMU with `-d int,cpu_reset -D <log_path>`
(add `-no-reboot` so a triple fault stops the VM instead of looping).
Decodes the exception chain (vector names, page-fault and selector error
codes, CR2), filters out timer IRQs and software interrupts, points at
the root cause, and symbolizes addresses when elf is given. x86 only.

Input parameters:

- `elf`
- `log_path` (string, required)
- `max_events` (integer)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/0xmortuex-gdbstub-mcp/gdbstub-mcp#diagnostics

## Score history

- 2026-10-17: 75
- 2026-10-16: 75
- 2026-10-15: 75
- 2026-10-14: 60
- 2026-10-13: 49
- 2026-10-12: 49

## Common questions

### What is the io.github.0xmortuex/gdbstub-mcp server?

io.github.0xmortuex/gdbstub-mcp is listed in the public MCP registry as io.github.0xmortuex/gdbstub-mcp. Debug kernels through QEMU's gdbstub with no gdb binary - and explain triple faults. This page covers its PyPI package (gdbstub-mcp).

### Is the io.github.0xmortuex/gdbstub-mcp server safe to use?

io.github.0xmortuex/gdbstub-mcp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. 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.0xmortuex/gdbstub-mcp server expose?

io.github.0xmortuex/gdbstub-mcp exposes 18 tools: debug_connect, debug_disconnect, debug_sessions, debug_registers, debug_set_register, and 13 more. Their descriptions and schemas cost roughly 1,372 tokens of context every time the server is loaded.

### Is the io.github.0xmortuex/gdbstub-mcp server still maintained?

io.github.0xmortuex/gdbstub-mcp is still listed as active in the MCP registry. We last reached this channel on 17 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.0xmortuex/gdbstub-mcp server under?

io.github.0xmortuex/gdbstub-mcp 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

- PyPI project: https://pypi.org/project/gdbstub-mcp/
- Socket report: https://socket.dev/pypi/package/gdbstub-mcp
- Repository: https://github.com/0xmortuex/gdbstub-mcp
- Changelog RSS feed: https://verifymcp.io/servers/0xmortuex-gdbstub-mcp/gdbstub-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/0xmortuex-gdbstub-mcp/gdbstub-mcp.json
- HTML version of this page: https://verifymcp.io/servers/0xmortuex-gdbstub-mcp/gdbstub-mcp