M
modelcontextprotocol/registry
Community registry of MCP servers
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Remote endpoint (mcpServers - Claude Desktop / Cursor / Windsurf)
{
"mcpServers": {
"modelcontextprotocol-registry": {
"url": "https://business-contact-finder-mcp.ottobot2025.workers.dev/mcp"
}
}
}Paste this into the mcpServers config of Claude Desktop or Cursor. The endpoint comes from public evidence; we do not install or host it. Official Registry record: this endpoint lists no request headers. That is not the same as key-free - the project docs decide.
VS Code (.vscode/mcp.json - the key is servers, remote needs type: http)
{
"servers": {
"modelcontextprotocol-registry": {
"type": "http",
"url": "https://business-contact-finder-mcp.ottobot2025.workers.dev/mcp"
}
}
}VS Code differs from the other three: the top-level key is <code>servers</code> and a remote endpoint also needs <code>"type": "http"</code>. Paste into .vscode/mcp.json.
Claude Code (command line)
claude mcp add --transport http modelcontextprotocol-registry https://business-contact-finder-mcp.ottobot2025.workers.dev/mcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
# MCP Registry
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation
## Development Status
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!
2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). 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 or in the #registry-dev Discord (joining details here).
Registry Working Group:
Radoslav (Rado) Dimitrov (Stacklok) @rdimitrov - WG Lead
Tadas Antanavicius (PulseMCP) @tadasant
Bob Dickinson (TeamSpark) @BobDickinson
Preeti (Pree) Dewani (Ravenmail) @pree-dew
## Contributing
We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.
Often (but not always) ideas flow through this pipeline:
Discord - Real-time community discussions
Discussions - Propose and discuss product/technical requirements
Issues - Track well-scoped technical work
Pull Requests - Contribute work towards issues
### Quick start:
#### Pre-requisites
Docker
Go - version per the go directive in go.mod; the Go toolchain fetches it for you
ko - Container image builder for Go (installation instructions)
golangci-lint - version per the golangci-lint-action pin in ci.yml, so local lint matches CI
#### Running the server
bash
# Start full development environment
make dev-compose
This starts the registry at localhost: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.
Note: The registry uses ko 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.
By 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 MCPREGISTRYSEEDFROM=data/seed.json MCPREGISTRYENABLEREGISTRYVALIDATION=false make dev-compose.
The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.
Alternative: Running a pre-built Docker image
Pre-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 MCPREGISTRYDATABASEURL (see docker-compose.yml for a working example):
📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation
## Development Status
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!
2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). 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 or in the #registry-dev Discord (joining details here).
Registry Working Group:
Radoslav (Rado) Dimitrov (Stacklok) @rdimitrov - WG Lead
Tadas Antanavicius (PulseMCP) @tadasant
Bob Dickinson (TeamSpark) @BobDickinson
Preeti (Pree) Dewani (Ravenmail) @pree-dew
## Contributing
We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.
Often (but not always) ideas flow through this pipeline:
Discord - Real-time community discussions
Discussions - Propose and discuss product/technical requirements
Issues - Track well-scoped technical work
Pull Requests - Contribute work towards issues
### Quick start:
#### Pre-requisites
Docker
Go - version per the go directive in go.mod; the Go toolchain fetches it for you
ko - Container image builder for Go (installation instructions)
golangci-lint - version per the golangci-lint-action pin in ci.yml, so local lint matches CI
#### Running the server
bash
# Start full development environment
make dev-compose
This starts the registry at localhost: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.
Note: The registry uses ko 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.
By 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 MCPREGISTRYSEEDFROM=data/seed.json MCPREGISTRYENABLEREGISTRYVALIDATION=false make dev-compose.
The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.
Alternative: Running a pre-built Docker image
Pre-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 MCPREGISTRYDATABASEURL (see docker-compose.yml for a working example):
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/modelcontextprotocol-registry/)
- Source
- awesome · https://github.com/modelcontextprotocol/registry
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.