Typed async Python client for the MCP Server Registry API
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":"mcp-registry-sdk","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-registry-sdk [](https://pypi.org/project/mcp-registry-sdk/) [](https://pypi.org/project/mcp-registry-sdk/) [](https://github.com/ukw2d/mcp_registry_sdk/actions/workflows/ci.yml) [](https://docs.astral.sh/ruff/) [](https://mypy-lang.org/) [](LICENSE) [](#mcp-registry-sdk) > Typed, async Python SDK for the **MCP Server Registry** REST API. Import name: `mcpreg`. **Unaffiliated community implementation.** This SDK is an independent, third-party project. It is **not** affiliated with, endorsed by, or sponsored by Anthropic, the Model Context Protocol team, or the maintainers of the official registry at `registry.modelcontextprotocol.io`. "Model Context Protocol", "MCP" and "MCP Server Registry" refer to the open specification this package targets; all trademarks remain with their owners. Spec quotations are for interoperability only. Python is the gap the registry itself acknowledges: its community-clients list covers Go, TypeScript and Java, and the official `mcp` package on PyPI is the *protocol* SDK (JSON-RPC, transports, tools) — no registry code. ## Highlights | Area | What you get | |---|---| | 🧱 **Models** | All 15 `server.json` schema definitions, plus the `ServerList`/`ServerResponse` envelope. Lenient on parse, strict on construct; unknown fields round-trip. | | 🔎 **Read client** | `RegistryClient` for the three `GET` endpoints with auto-paging, opaque-cursor handling, and a typed exception hierarchy. | | ✍…
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.