World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Debug kernels through QEMU's gdbstub with no gdb binary - and explain triple faults.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 4/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 11/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Gdbstub MCP. Follow https://mcp.popnx.com/i/0xmortuex-gdbstub-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Gdbstub MCP for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "gdbstub": { "command": "uvx", "args": [ "gdbstub-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Gdbstub MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
SettingsDeveloperEdit Config
{
"mcpServers": {
"gdbstub": {
"command": "uvx",
"args": [
"gdbstub-mcp"
]
}
}
}Use Gdbstub MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Gdbstub MCP or shows a Gdbstub MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Gdbstub MCP yet
Gdbstub MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Gdbstub MCP
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Gdbstub MCP for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user gdbstub -- uvx gdbstub-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Gdbstub MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user gdbstub -- uvx gdbstub-mcpYou should see Gdbstub MCP listed as connected
Use Gdbstub MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Gdbstub MCP or shows a Gdbstub MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Gdbstub MCP for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "gdbstub": { "command": "uvx", "args": [ "gdbstub-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Gdbstub MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use Gdbstub MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Gdbstub MCP or shows a Gdbstub MCP tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Gdbstub MCP for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "gdbstub": { "type": "stdio", "command": "uvx", "args": [ "gdbstub-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Gdbstub MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use Gdbstub MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Gdbstub MCP or shows a Gdbstub MCP tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user gdbstub -- uvx gdbstub-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"gdbstub": {
"command": "uvx",
"args": [
"gdbstub-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"gdbstub": {
"command": "uvx",
"args": [
"gdbstub-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"gdbstub": {
"type": "stdio",
"command": "uvx",
"args": [
"gdbstub-mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account 0xmortuex, which owns the repo
Code last changed 39 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for gdbstub-mcp@0.1.0
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/0xmortuex-gdbstub-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 39 days ago, and the latest version (0.1.0) reached the registry 39 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Gdbstub MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Let your AI agent debug a kernel, and tell you why it triple-faulted.
gdbstub-mcp is an MCP server that gives AI agents (Claude Code, or any MCP client) a debugger for bare-metal code running in QEMU. It speaks the GDB Remote Serial Protocol directly to QEMU's built-in gdbstub, so you don't need a gdb binary. That matters most on Windows and macOS, where a cross-architecture gdb is a pain to get.
It's the companion to qemu-mcp. qemu-mcp lets an agent boot a kernel and *see* the crash. gdbstub-mcp lets it find out *why*.
An agent debugging a hobby kernel. This is real output, captured from the test kernel in tests/fixtures/kernel:
> debug_break kernel.c:10
#1 sw breakpoint at 0x100029 at kernel.c:10
debug_continue
Stopped: SIGTRAP (breakpoint/step) - breakpoint #1 (kernel.c:10) pc = 0x100029 at kernel.c:10 next: mov eax, dword ptr [ebp + 8]
debug_backtrace
#0 0x100029 at kernel.c:10 #1 0x100071 at kernel.c:16 #2 0x1000b2 at kernel.c:28 #3 0x100016 <_start+0xa> at boot.s:21
debug_registers eip,eflags,cr0
eip = 0x00100029 at kernel.c:10 eflags = 0x00000093 [SF AF CF] cr0 = 0x00000011 [ET PE]
And when the machine silently reboots, debug_explain_fault reads QEMU's interrupt log and explains the crash:
> debug_explain_fault
A TRIPLE FAULT occurred: the CPU reset itself.
[0] #UD invalid opcode at triple_fault+0xa (kernel.c:23) [1] #GP general protection fault at triple_fault+0xa (kernel.c:23) selector 0x32: IDT entry 6 = #UD -> the IDT entry for vector 0x6 is missing or invalid - the CPU couldn't even start your handler. ... [2] #DF double fault at triple_fault+0xa (kernel.c:23)
Root cause: the chain started with #UD at triple_fault+0xa. It escalated to a triple fault because the handler for #UD (IDT entry 0x6) could not be invoked. Fix the IDT entry so the original exception reaches your handler, then fix the #UD itself.
A real QEMU log of a crash is thousands of lines of timer interrupts and register dumps. This tool picks out the exception chain, decodes the error codes, and points at the cause.
Existing GDB MCP servers wrap a gdb binary and target userland programs or core dumps. The embedded ones target microcontrollers through probe-rs or OpenOCD. None of them is built for the osdev loop: a kernel you wrote yourself, running in QEMU, crashing before it can print anything.
pyelftools + capstone). Run pip install gdbstub-mcp and you're set.target.xml. Control registers (CR0/CR2/CR3/CR4, EFER) are there on x86, and flag registers are decoded.kmain, kmain+0x10 or kernel.c:42, and every stop shows function+offset at file:line. Prefixed ABIs work too: kmain resolves to mort_kmain when that name is unique.-O2 kernels without frame pointers it can scan the stack for return addresses instead.debug_explain_fault, described above. I haven't found another tool that does this.pip install gdbstub-mcp
Claude Code:
claude mcp add gdbstub -- gdbstub-mcp
Other MCP clients use the same idea: run gdbstub-mcp as a stdio server. Python 3.10+.
Start QEMU with its gdbstub on, with the CPU halted:
qemu-system-i386 -kernel kernel.elf -s -S -d int,cpu_reset -D int.log -no-reboot
-s opens the stub on tcp::1234.-S halts the CPU before the first instruction.-d int,cpu_reset -D int.log -no-reboot is only needed for debug_explain_fault.With qemu-mcp, pass the same flags through qemu_boot's extra_args: extra_args="-s -S -d int,cpu_reset -D int.log -no-reboot".
Then ask your agent something like *"connect to the kernel with kernel.elf, break in kmain, and step until the page fault"*.
Addresses can be written as 0x1234, symbol, symbol+0x10, file.c:42 or $esp+8.
| Tool | What it does |
|---|---|
debug_connect | Connect to a gdbstub (port, default 1234) and optionally load an elf with symbols. Several named sessions can be open at once. |
debug_disconnect | Remove breakpoints, detach (the guest keeps running) and close the session. |
debug_sessions | List sessions: endpoint, running or halted, ELF, breakpoint count. |
debug_registers | Read registers: a chosen list, the general set, or all=True for control, segment and FPU registers. Flags are decoded and pointers symbolized. |
debug_set_register | Write a register. |
debug_memory | Read memory as a hexdump, as symbolized pointer-sized words, or as a string. |
debug_write_memory | Write bytes. |
debug_break | Set a breakpoint (sw, or hw for code before paging or not yet loaded) or a watchpoint (write, read, access). |
debug_delete / debug_breakpoints | Remove a breakpoint, or list them all. |
debug_continue | Resume and wait up to timeout_s for a stop. If no stop comes, the target keeps running. |
debug_wait / debug_interrupt | Keep waiting for a stop, or halt the target now (like Ctrl-C). |
debug_step | Single-step N instructions. |
debug_backtrace | Call stack by frame-pointer chain (fp), stack scan (scan), or auto. |
debug_disassemble | Disassemble at an address or the pc. bits=16 decodes real-mode code. |
debug_symbol | Look up an address, symbol or line offline, with no target needed. |
debug_explain_fault | Explain a crash or triple fault from a QEMU -d int,cpu_reset log (x86). |
next/finish, and no local variables or C expressions yet (see BACKLOG.md). You get symbols, lines, registers, memory and disassembly, which covers most kernel debugging.call inside a known function, so stale frames can appear. Build with -fno-omit-frame-pointer for exact backtraces.debug_explain_fault understands x86 logs only.pip install ".[test]" anyio "ruff==0.16.0" "mypy==2.3.0"
ruff check src tests && mypy --strict src pytest tests
Unit tests use a fake gdbstub on a real TCP socket, plus a real QEMU log of a triple fault, so they need no QEMU. tests/test_qemu_integration.py boots the fixture kernel in real QEMU (CI installs qemu-system-x86). It checks breakpoints, watchpoints, line numbers, a 4-deep backtrace and an end-to-end triple fault, and skips itself if QEMU isn't installed. To rebuild the fixture kernel, run python tests/fixtures/kernel/build.py, which needs pip install ziglang.
MIT