Guide
MCP registries compared
Different MCP directories optimize for different things. This table summarizes the major ones as we understand them; corrections welcome via the takedown/contact page.
| Registry | Coverage | Install | Token cost | Security |
|---|---|---|---|---|
| Official MCP registry | Open, verified namespaces | Metadata + package pointers | — | — |
| GitHub MCP registry | Curated | One-click VS Code / Copilot | — | — |
| Glama | Large index | Config JSON, tools list | Partial | — |
| Smithery | Large index + hosting | CLI install, hosted servers | — | — |
| mcp.so | Large community index | Config JSON | — | — |
| PulseMCP | Curated index + newsletter | Remote endpoints | — | — |
| MCPSkillHub | Official registry + GitHub lists + npm, merged | Snippets for 5 clients | Measured (sandbox) | Measured, with findings |
Why we built another one
Connecting an MCP server costs context: every tool definition is resent to the model on each turn. Servers also run with your credentials. We think the useful question isn't just “which servers exist?” but “which ones are lean, maintained and safe to connect?” — so we measure that.