Local-first MCP server that gives AI coding agents a memory of fixed bugs: record at fix time, retrieve before coding, search while debugging, enforce with Semgrep.
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":"bugledger-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.
<p align="center"> <img alt="Bug Ledger" src="https://raw.githubusercontent.com/xajeel/bugledger-mcp/main/artifacts/logo/mark.svg" width="96"> </p> # Bug Ledger <p align="center"> <strong>Never fix the same bug twice.</strong><br> A local MCP server that gives AI coding agents a permanent memory of the bugs you already fixed. </p> <p align="center"> <a href="https://pypi.org/project/bugledger-mcp/"><img alt="PyPI" src="https://img.shields.io/pypi/v/bugledger-mcp?color=6366F1"></a> <a href="https://pypi.org/project/bugledger-mcp/"><img alt="Python" src="https://img.shields.io/pypi/pyversions/bugledger-mcp"></a> <a href="https://github.com/xajeel/bugledger-mcp/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/xajeel/bugledger-mcp/actions/workflows/ci.yml/badge.svg"></a> <a href="https://github.com/xajeel/bugledger-mcp/blob/main/LICENSE"><img alt="License" src="https://img.shields.io/badge/license-MIT-14B8A6"></a> </p> ## What it does Your agent fixes a bug. You confirm the record. From then on, every session on that project checks the ledger before writing code in that area and can search it while debugging. - **Before coding**, the agent calls `get_patterns` and sees the past bugs for that feature area. - **While debugging**, it calls `search_bugs` with the error text. - **After a fix**, you run `/logbug`. The agent drafts the record, you approve, it is stored. Everything stays on your machine: one SQLite file in `~/.bugledger/`. No account, no cloud, no telemetry. ## Install Requires [uv](https://docs.astral.sh/uv/). It downloads Python if needed. **Claude Code** ```sh claude mcp add bugledger -- uvx bugledger-mcp ``` **Cursor**, in `.cursor/mcp.json`: ```json { "mcpServers": { "bugledger": { "command": "uvx", "args": ["bugledger-mcp"] } } } ``` **Any other MCP client:** command `uvx`, argument `bugledger-mcp`, transport stdio. **Whole team:** commit that JSON as `.mcp.json` (Claude Code) or `.cursor/mcp.json` (Cursor) in …
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.