In November 2024, Anthropic released the Model Context Protocol —
a standard that lets AI agents call external tools. Within months,
hundreds of MCP servers appeared on GitHub. Stripe, Grafana,
Cloudflare, AWS — all publishing official servers.
The problem: there was nowhere to find them.
Developers were digging through GitHub search, Reddit threads,
and scattered READMEs to find servers that might already exist.
The official Anthropic registry had an API but no UI.
The most starred community lists had tens of thousands of
GitHub stars but weren't searchable or filterable.
This is the npm problem from 2012. A growing ecosystem
with no discovery layer.
What we built
MCPNest indexes MCP servers from the official Anthropic registry
and GitHub. 7,554 servers as of today, with quality scores,
install counts, compatibility flags per client, and one-click
install configs for Claude Desktop, Cursor, VS Code, and Windsurf.
Every server page renders the GitHub README, shows the install
config for each client, and tracks installs via a copy button
that increments a counter in Supabase.
Quality scoring
Not all MCP servers are equal. We score each server 0-100 based on:
- Has a valid install config
- Has a description
- Is verified from the official registry
- GitHub stars
- Install count
The score maps to an A-F grade shown on each server card.
What this doesn't solve
Discovery is the easy part. Finding a server is step one.
The harder problems are: running it reliably, giving your team
access to it securely, and managing it at scale.
That's what we built next.
→ mcpnest.io
Top comments (0)