It is 1 AM and you need a Postgres MCP server. Not a list of Postgres MCP servers: the one you should actually run. You check five directories and get five different answers. One sorts alphabetically, one sorts by GitHub stars, one shows you 400 results with a search box, one shows a curated fifteen, and one quietly ranks its own sponsor first.
Supply was never the problem. There are tens of thousands of MCP servers and agent skills on GitHub right now. The problem is that "which one" is a data question, and most registries answer it with vibes.
I build one of these directories, so consider this both a field guide and a confession. Here is what each major registry is actually for, with the receipts.
The landscape, honestly
The official MCP Registry (registry.modelcontextprotocol.io) is the canonical namespace. It is machine-first: a JSON API of server manifests with exact install metadata, maintained under the Model Context Protocol org. What it deliberately is not: a ranking. There is no "best", no adoption data, no editorial. If you publish a server, you should absolutely be in it. It is the closest thing MCP has to npm's registry. But if you are choosing a server, it cannot tell you which of the four Notion entries people actually use.
mcpmarket.com is the volume play, and credit where due: they registered the domain two days after Anthropic announced MCP in November 2024, and 19 months of compounding first-mover authority shows. Their sitemap advertises roughly 38,000 server pages and around 250,000 skill pages, they publish daily top-10 lists, and they localize into four languages. Two things worth knowing as a user. First, rankings are by GitHub stars, a popularity proxy that ignores whether anyone installs the thing. Second, their robots.txt blocks AI crawlers like GPTBot, ClaudeBot, CCBot and Google-Extended: a deliberate trade that keeps their content out of the corpora your AI assistant learns from. That is their right. It also means the place many developers now ask first ("Claude, what's a good Postgres MCP server?") increasingly cannot cite them.
mcp.so was one of the first community directories and is still one of the largest link collections. It is a good breadth-first sweep. Its answer to "which one" is mostly "here are all of them."
Glama approaches from the client side. It is an AI workspace that happens to maintain a solid MCP server directory with quality signals attached. If you live in Glama, its directory is conveniently close to where you run things.
Smithery is the hosted angle: less "directory", more "we run the server for you." That is genuinely useful when you do not want to babysit processes, and beside the point when you are picking open-source software to run yourself.
Skillselion (skillselion.com) is ours, so grade this paragraph hardest. The bet is different: rank everything by real adoption. 81,864 tools tracked (agent skills, MCP servers, marketplaces) with 125 million recorded installs from the skills.sh registry and GitHub, refreshed daily. The Top 100 is one stable, install-ranked list. Per-vendor pages like the best Postgres MCP servers come with a hand-written verdict, and every vendor page is required to include the vendor's official server, marked OFFICIAL, because a "best Notion servers" page without Notion's own server is theater. Where install data does not exist (most MCP servers report none), we say so and rank by stars instead of pretending. All of it is open to every AI crawler, deliberately: the opposite trade from mcpmarket's.
Two takeaways worth arguing about
1. Catalogs answered 2024's question. Rankings answer 2026's. When there were 500 servers, "a big list" was the product. At 50,000+, the list is a commodity; GitHub search is a list. The scarce thing is trustworthy ordering: install counts, freshness, dead-repo pruning, duplicate collapsing. Judge any registry by whether its #1 result carries evidence, not by its total.
2. A registry that blocks AI crawlers is invisible in the place developers now ask. Developers increasingly pick tools by asking their assistant, not by browsing directories. Whatever you think of AI training economics, blocking GPTBot and ClaudeBot means the assistant answering "which Postgres MCP server?" literally cannot read your rankings. Watch this become the quiet dividing line between registries over the next year.
The boring, practical answer
Publish to the official registry (canonical), then check an adoption-ranked directory before installing anything with filesystem or network access. If you want the current state of the ecosystem in numbers (how many servers, skills and marketplaces exist, and what people actually install), the data report is free to cite: The State of AI Agent Skills 2026.
And if your server made a Top 100 or a vendor page, there is a badge for your README. Backlinks are the oldest ranking system there is.
Disclosure: I build Skillselion. Every number above is either from a public file you can check (sitemaps, robots.txt, the registry API) or from our live catalog, dated July 9, 2026. Skillselion is an independent directory, not affiliated with Anthropic, OpenAI, or any vendor named here.
Top comments (0)