| Filename | Latest commit message | Latest commit date |
|---|---|---|
e0aecadc24Updates the registry type for all Docker Hub packages in the seed data from `docker-hub` to `oci` to align with the standardized OCI registry format. This change affects the `registry_type` field and simplifies the `identifier` field by removing the full Docker Hub URL prefix. Changes: - Updated `registry_type` from `docker-hub` to `oci` for all Docker packages - Simplified `identifier` field to use just the repository name/path instead of full URLs - Maintained `registry_base_url` as `https://docker.io` for all entries This refactoring improves consistency and aligns with OCI standards while maintaining backward compatibility through the registry base URL. |
||
| .. | ||
| server-json | ||
| server-registry-api | ||
| admin-operations.md | ||
| architecture.md | ||
| design_principles.md | ||
| ecosystem-diagram.excalidraw.svg | ||
| faq.md | ||
| MCP Developers Summit 2025 - Registry Talk Slides.pdf | ||
| moderation-guidelines.md | ||
| new_package_registry.md | ||
| README.md | ||
| roadmap.md | ||
| versioning.md | ||
Official Registry Documentation
This extends the main README.
Project Documentation
faq.md- Frequently asked questions about the MCP Registrydesign_principles.md- Core constraints and principles guiding the registry designroadmap.md- High-level roadmap for the MCP Registry developmentMCP Developers Summit 2025 - Registry Talk Slides.pdf- Slides from a talk given at the MCP Developers Summit on May 23, 2025, with an up-to-date vision of how we are thinking about the official registry.
API & Technical Specifications
openapi.yaml- OpenAPI specification for the official registry APIapi_examples.md- Examples of what data will actually look like coming from the official registry APIarchitecture.md- Technical architecture, deployment strategies, and data flowsserver.jsonREADME - description of theserver.jsonpurpose and schemanew_package_registry.md- steps to add a new package registry for local server packages