Local Python docs MCP server, accelerated with Rust
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":"pydocs-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.
# <img src="assets/icon.png" width="120"> pydocs-mcp [](https://github.com/msobroza/pydocs-mcp/actions/workflows/ci.yml) [](https://pypi.org/project/pydocs-mcp/) [](https://www.python.org/downloads/) [](LICENSE) [](https://github.com/astral-sh/ruff) [](https://mypy-lang.org/) [](https://modelcontextprotocol.io) [](https://msobroza.github.io/pydocs-mcp/) **Local, version-aware code & docs search for your AI coding agent — over the exact library versions installed on your machine.** 📖 **Full documentation: [msobroza.github.io/pydocs-mcp](https://msobroza.github.io/pydocs-mcp/)** — built from [`documentation/`](documentation/).  Your AI assistant thinks you're on `requests` 2.28. You actually have 2.31. It calls a kwarg that was renamed two versions ago, your test fails, and you lose twenty minutes. The fix isn't a smarter prompt — it's giving the AI docs that match **your lockfile**, not the average of every StackO…
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.