[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-73189":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":23,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":28,"readmeContent":29,"aiSummary":30,"trendingCount":16,"starSnapshotCount":16,"syncStatus":31,"lastSyncTime":32,"discoverSource":33},73189,"registry","modelcontextprotocol\u002Fregistry","modelcontextprotocol","A community driven registry service for Model Context Protocol (MCP) servers.","https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Fregistry\u002Ftree\u002Fmain\u002Fdocs",null,"Go",6913,851,80,88,0,19,36,115,57,39.79,"Other",false,"main",[26,27],"mcp","mcp-servers","2026-06-12 02:03:10","# MCP Registry\n\nThe MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.\n\n[**📤 Publish my MCP server**](docs\u002Fmodelcontextprotocol-io\u002Fquickstart.mdx) | [**⚡️ Live API docs**](https:\u002F\u002Fregistry.modelcontextprotocol.io\u002Fdocs) | [**👀 Ecosystem vision**](docs\u002Fdesign\u002Fecosystem-vision.md) | 📖 **[Full documentation](.\u002Fdocs)**\n\n## Development Status\n\n**2025-10-24 update**: The Registry API has entered an **API freeze (v0.1)** 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!\n\n**2025-09-08 update**: The registry has launched in preview 🎉 ([announcement blog post](https:\u002F\u002Fblog.modelcontextprotocol.io\u002Fposts\u002F2025-09-08-mcp-registry-preview\u002F)). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in [GitHub discussions](https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Fregistry\u002Fdiscussions\u002Fnew?category=ideas) or in the [#registry-dev Discord](https:\u002F\u002Fdiscord.com\u002Fchannels\u002F1358869848138059966\u002F1369487942862504016) ([joining details here](https:\u002F\u002Fmodelcontextprotocol.io\u002Fcommunity\u002Fcommunication)).\n\nCurrent key maintainers:\n- **Adam Jones** (Anthropic) [@domdomegg](https:\u002F\u002Fgithub.com\u002Fdomdomegg)  \n- **Tadas Antanavicius** (PulseMCP) [@tadasant](https:\u002F\u002Fgithub.com\u002Ftadasant)\n- **Toby Padilla** (GitHub) [@toby](https:\u002F\u002Fgithub.com\u002Ftoby)\n- **Radoslav (Rado) Dimitrov** (Stacklok) [@rdimitrov](https:\u002F\u002Fgithub.com\u002Frdimitrov)\n\n## Contributing\n\nWe use multiple channels for collaboration - see [modelcontextprotocol.io\u002Fcommunity\u002Fcommunication](https:\u002F\u002Fmodelcontextprotocol.io\u002Fcommunity\u002Fcommunication).\n\nOften (but not always) ideas flow through this pipeline:\n\n- **[Discord](https:\u002F\u002Fmodelcontextprotocol.io\u002Fcommunity\u002Fcommunication)** - Real-time community discussions\n- **[Discussions](https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Fregistry\u002Fdiscussions)** - Propose and discuss product\u002Ftechnical requirements\n- **[Issues](https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Fregistry\u002Fissues)** - Track well-scoped technical work  \n- **[Pull Requests](https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Fregistry\u002Fpulls)** - Contribute work towards issues\n\n### Quick start:\n\n#### Pre-requisites\n\n- **Docker**\n- **Go 1.24.x**\n- **ko** - Container image builder for Go ([installation instructions](https:\u002F\u002Fko.build\u002Finstall\u002F))\n- **golangci-lint v2.4.0**\n\n#### Running the server\n\n```bash\n# Start full development environment\nmake dev-compose\n```\n\nThis starts the registry at [`localhost:8080`](http:\u002F\u002Flocalhost:8080) with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.\n\n**Note:** The registry uses [ko](https:\u002F\u002Fko.build) to build container images. The `make dev-compose` command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.\n\nBy default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with `MCP_REGISTRY_SEED_FROM=data\u002Fseed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose`.\n\nThe setup can be configured with environment variables in [docker-compose.yml](.\u002Fdocker-compose.yml) - see [.env.example](.\u002F.env.example) for a reference.\n\n\u003Cdetails>\n\u003Csummary>Alternative: Running a pre-built Docker image\u003C\u002Fsummary>\n\nPre-built Docker images are automatically published to GitHub Container Registry. Note that the image does not bundle PostgreSQL, so you need to run your own and point the registry at it via `MCP_REGISTRY_DATABASE_URL` (see [docker-compose.yml](.\u002Fdocker-compose.yml) for a working example):\n\n```bash\n# Run latest stable release\ndocker run -p 8080:8080 ghcr.io\u002Fmodelcontextprotocol\u002Fregistry:latest\n\n# Run latest from main branch (continuous deployment)\ndocker run -p 8080:8080 ghcr.io\u002Fmodelcontextprotocol\u002Fregistry:main\n\n# Run specific release version\ndocker run -p 8080:8080 ghcr.io\u002Fmodelcontextprotocol\u002Fregistry:v1.0.0\n\n# Run development build from main branch\ndocker run -p 8080:8080 ghcr.io\u002Fmodelcontextprotocol\u002Fregistry:main-20250906-abc123d\n```\n\n**Available tags:** \n- **Releases**: `latest`, `v1.0.0`, `v1.1.0`, etc.\n- **Continuous**: `main` (latest main branch build)\n- **Development**: `main-\u003Cdate>-\u003Csha>` (specific commit builds)\n\n\u003C\u002Fdetails>\n\n#### Publishing a server\n\nTo publish a server, we've built a simple CLI. You can use it with:\n\n```bash\n# Build the latest CLI\nmake publisher\n\n# Use it!\n.\u002Fbin\u002Fmcp-publisher --help\n```\n\nSee [the publisher guide](.\u002Fdocs\u002Fmodelcontextprotocol-io\u002Fquickstart.mdx) for more details.\n\n#### Other commands\n\n```bash\n# Run lint, unit tests and integration tests\nmake check\n```\n\nThere are also a few more helpful commands for development. Run `make help` to learn more, or look in [Makefile](.\u002FMakefile).\n\n\u003C!--\nFor Claude and other AI tools: Always prefer make targets over custom commands where possible.\n-->\n\n## Architecture\n\n### Project Structure\n\n```\n├── cmd\u002F                     # Application entry points\n│   └── publisher\u002F           # Server publishing tool\n├── data\u002F                    # Seed data\n├── deploy\u002F                  # Deployment configuration (Pulumi)\n├── docs\u002F                    # Documentation\n├── internal\u002F                # Private application code\n│   ├── api\u002F                 # HTTP handlers and routing\n│   ├── auth\u002F                # Authentication (GitHub OAuth, JWT, namespace blocking)\n│   ├── config\u002F              # Configuration management\n│   ├── database\u002F            # Data persistence (PostgreSQL)\n│   ├── service\u002F             # Business logic\n│   ├── telemetry\u002F           # Metrics and monitoring\n│   └── validators\u002F          # Input validation\n├── pkg\u002F                     # Public packages\n│   ├── api\u002F                 # API types and structures\n│   │   └── v0\u002F              # Version 0 API types\n│   └── model\u002F               # Data models for server.json\n├── scripts\u002F                 # Development and testing scripts\n├── tests\u002F                   # Integration tests\n└── tools\u002F                   # CLI tools and utilities\n    └── validate-*.sh        # Schema validation tools\n```\n\n### Authentication\n\nPublishing supports multiple authentication methods:\n- **GitHub OAuth** - For publishing by logging into GitHub\n- **GitHub OIDC** - For publishing from GitHub Actions\n- **DNS verification** - For proving ownership of a domain and its subdomains\n- **HTTP verification** - For proving ownership of a domain\n\nThe registry validates namespace ownership when publishing. E.g. to publish...:\n- `io.github.domdomegg\u002Fmy-cool-mcp` you must login to GitHub as `domdomegg`, or be in a GitHub Action on domdomegg's repos\n- `me.adamjones\u002Fmy-cool-mcp` you must prove ownership of `adamjones.me` via DNS or HTTP challenge\n\n## Community Projects\n\nCheck out [community projects](docs\u002Fcommunity-projects.md) to explore notable registry-related work created by the community.\n\n## More documentation\n\nSee the [documentation](.\u002Fdocs) for more details if your question has not been answered here!\n","MCP Registry是一个为Model Context Protocol (MCP) 服务器提供注册服务的社区驱动平台，类似于MCP服务器的应用商店。该项目使用Go语言开发，支持用户发布自己的MCP服务器，并通过API向客户端提供服务器列表。其核心功能包括稳定的API版本管理（当前处于v0.1冻结期），确保在一段时间内不会出现破坏性变更，便于开发者集成。此外，它还提供了实时API文档和详细的开发指南。MCP Registry适用于需要发现和连接不同MCP服务器的各种应用场景，如机器学习模型部署、微服务架构等。项目活跃度高，拥有明确的贡献流程和社区支持渠道，适合希望参与开源项目的开发者加入。",2,"2026-06-11 03:44:25","high_star"]