There are now five places that call themselves "the MCP marketplace". They differ in curation, signing, search and how aggressively they vendor-pitch you. Here is a head-to-head look at where to actually find servers in 2026.
Why the marketplace question matters
An MCP server is privileged code. Where you get it from is a security control as much as a discoverability one. A maintained, signed registry with reputation signals beats a Google search every time. The five places below are roughly in order of how often we use them.
The contenders
1. Loadout (this site)
Curated, human-reviewed directory of 130+ servers grouped into 13 categories. Verifies maintainer fingerprints, surfaces install commands as one-click copy. Indexes both stdio and HTTP+SSE remote servers.
- Strengths: editorial curation, detailed pages, comparison tables, long-form guides.
- Weaknesses: smaller catalogue than auto-scrapers — 130 vs 1000+.
- Best for: finding a battle-tested server fast, with safety context.
2. Smithery
Auto-indexes public MCP servers, supports one-click install for many clients. Wide catalogue.
- Strengths: breadth (1000+ entries), built-in install handler protocol.
- Weaknesses: low signal on quality and trust; many dead listings.
- Best for: discovering niche servers when you already know what you want.
3. mcp.so
Community-maintained directory with category navigation. Good for browsing.
- Strengths: chronological feed of new servers, comments.
- Weaknesses: minimal vetting, occasional broken links.
- Best for: seeing what just launched.
4. modelcontextprotocol/servers (GitHub)
The official Anthropic-maintained reference implementations. ~25 first-party servers, all open source.
- Strengths: maximum trust signal — official source.
- Weaknesses: tiny catalogue compared to community.
- Best for: blue-chip integrations (filesystem, GitHub, Slack, memory).
5. PulseMCP
Newsletter-plus-directory hybrid. Strong editorial voice on what is happening in the space week by week.
- Strengths: context on releases, not just listings.
- Weaknesses: directory is secondary to the newsletter.
- Best for: staying current.
Side-by-side feature table
| Marketplace | Listings | Curation | Signing | Search | Install UX |
|---|---|---|---|---|---|
| Loadout | 130+ | Editorial | Fingerprints | Faceted | Copy command |
| Smithery | 1000+ | Automated | Some | Keyword | One-click handler |
| mcp.so | 500+ | Community | None | Category | Manual copy |
| modelcontextprotocol/servers | ~25 | First-party | npm provenance | Repo only | README |
| PulseMCP | Selective | Editorial | None | Newsletter | Manual |
How to choose for your use case
Three rules of thumb:
- Production deployment → start with the official Anthropic repo or a curated directory. Pin versions. Audit dependencies.
- Exploratory tinkering → Smithery for breadth, mcp.so for what is new this week.
- Need context, not just install → Loadout pages and PulseMCP for editorial framing.
The trust gap nobody is closing yet
None of the marketplaces today do what npm provenance does for the broader Node ecosystem: cryptographic chain-of-custody from source to artifact. Until they do, treat any MCP install with the same scepticism you would treat a random Chrome extension. Read more in our supply chain attack guide.