I spent an afternoon digging through the MCP ecosystem numbers. Here is what I found.
The numbers
- 13,000+ MCP servers on npm and GitHub (as of May 2026)
- 97 million monthly SDK downloads — that is 3x from 6 months ago
- 400% YoY growth in new server registrations
- Anthropic official servers reach 48,500 downloads/month for filesystem alone
What this means
MCP is not just a protocol anymore. It is becoming the standard way to give AI models access to tools — databases, APIs, file systems, everything.
But here is the gap: discovery. Finding the right MCP server is still painful. You search npm with guesswork or dig through folders on GitHub.
What I built
npm install -g mcp-hub
mcp-hub search database
mcp-hub install @modelcontextprotocol/server-postgres
Six commands. Five official servers in the registry. Real packages, verified on npm.
What is next
- Private registries for enterprise teams
- Community submissions (open an issue if you want your server added)
- CI/CD integration for auto-publishing MCP servers
GitHub: GrahamduesCN/mcp-platform
September 28, 2026 — update on MCP ecosystem growth.
Top comments (1)
Verifying on npm solves the search part, but with 13k servers the hard part isn't finding a package name anymore. It's trust and version drift: which server is still maintained, what tools it claims to expose, and whether a minor bump silently changes behavior.
Does mcp-hub add metadata beyond npm's verification to answer that, or is it mainly a friendlier search over the same package data?