MCP Server for rr Reverse Debugging
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"karellen-rr-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MCP Server for rr Reverse Debugging (karellen-rr-mcp) [](https://gitter.im/karellen/Lobby) [](https://github.com/karellen/karellen-rr-mcp/actions/workflows/build.yml) [](https://coveralls.io/r/karellen/karellen-rr-mcp?branch=master) [](https://pypi.org/project/karellen-rr-mcp/) [](https://pypi.org/project/karellen-rr-mcp/) [](https://pypi.org/project/karellen-rr-mcp/) [](https://pypi.org/project/karellen-rr-mcp/) [](https://pypi.org/project/karellen-rr-mcp/) ## Overview `karellen-rr-mcp` is an [MCP](https://modelcontextprotocol.io/) (Model Context Protocol) server that enables any MCP-compliant LLM client to use [rr](https://rr-project.org/) for reverse debugging. Instead of iteratively adding debug output and rebuilding, the LLM can record a failing test with rr, then replay it with full forward and reverse debugging via GDB/MI, inspecting program state without modifying source code. ## Requirements - **Linux** on x86-64 (rr only supports Linux; aarch64 is experimental) - **[rr](https://rr-project.org/)** installed and on PATH - **[GDB](https://www.sourceware.org/gdb/)** installed and on PATH (used by rr for debugging) - **Python** >= 3.11 - **`perf_event_paranoid`** set to `1` to allow recording: ```bas…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.