io.github.0xmortuex/gdbstub-mcp
PYPI · GDBSTUB-MCP
Debug kernels through QEMU's gdbstub with no gdb binary - and explain triple faults.
Available components
Last scanned (4 hours ago)
Scores higher than 72% of PyPI servers
Category Developer Tools
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to 0xmortuex/gdbstub-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1532 tokens (~85/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
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.
- 15 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Oct 26 +11
- Malware scan: pass → unverified ▼ security
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 12 Oct 26 49
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 17 Oct 2026 · Analysed pypi/gdbstub-mcp@0.1.0
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | 0xmortuex/gdbstub-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/0xmortuex/gdbstub-mcp/.github/workflows/publish.yml@refs/tags/v0.1.0 |
| Rekor log index | 3206199314 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:b1092a59261915c11e05f4d4453e149bac201ef145534605a3ccb5241e1714f1 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| 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 →
debug_backtrace ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_frames | integer | – | – |
| mode | string | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_break ~117
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).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| length | – | – | – |
| location | string | yes | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_breakpoints ~23
List breakpoints and watchpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_connect ~211
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.
| Name | Type | Req | Description |
|---|---|---|---|
| elf | – | – | – |
| host | string | – | – |
| load_bias | integer | – | – |
| name | string | yes | – |
| port | integer | – | – |
| timeout_s | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_continue ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| timeout_s | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_delete ~32
Remove a breakpoint/watchpoint by its # id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_disassemble ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | – |
| bits | – | – | – |
| count | integer | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_disconnect ~41
Remove breakpoints, detach from the stub so the guest keeps running, and forget the session. A running target is halted first.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_explain_fault ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| elf | – | – | – |
| log_path | string | yes | – |
| max_events | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_interrupt ~28
Halt a running target immediately (like Ctrl-C in gdb).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_memory ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| format | string | – | – |
| length | integer | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_registers ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | – |
| name | string | yes | – |
| registers | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_sessions ~13
List active debug sessions.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_set_register ~48
Write a register. value is an address expression (0x10, symbol, ...).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| register | string | yes | – |
| value | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_step ~41
Single-step `count` machine instructions (1..1000) and show where it stopped.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_symbol ~93
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=).
| Name | Type | Req | Description |
|---|---|---|---|
| elf | – | – | – |
| name | – | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_wait ~37
Wait for a running target to stop (after debug_continue timed out).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| timeout_s | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
debug_write_memory ~51
Write raw bytes (hex string, e.g. "90 90 cc") to guest memory.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| hex_bytes | string | yes | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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.
pypi · gdbstub-mcp
claude mcp add 0xmortuex-gdbstub-mcp -- uvx gdbstub-mcp
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.