Apr 20, 20263 min readMCPfinder

Welcome to MCPfinder

Why we built another MCP directory, and what makes this one different — starting with a public reliability score on every listing.

There are already a few places you can go to browse MCP servers. Most of them are link dumps — a server name, a one-line description, maybe a category. That's fine if you're exploring. It's not fine if you're deciding what to put into production.

MCPfinder is the version of that directory we wanted ourselves.

The problem with "it exists"

A registry that just lists MCP servers answers "does this thing exist?" — not "does it work?" If you're a CTO looking at adding five MCP servers to your internal agent, the second question is the one that matters. You need to know:

  • Is the repository still maintained?
  • Does the license let us actually use it?
  • What's the install story for our runtime?
  • When was the last release?
  • Who else relies on it?

None of this is rocket science. But nobody was bothering to surface it in one place.

What we do differently

Every listing on MCPfinder has a public reliability score between 0 and 100. It's computed daily against a handful of signals — repo reachability, license, README quality, release cadence, maintainer activity, stars — and you can see the breakdown on every detail page. Scores under 40 get the listing flagged automatically, the vendor gets an email, and they have seven days to fix it before the listing disappears from search.

That single number is the difference between a directory and a decision tool.

What's here today

  • A clean homepage with featured and latest MCPs
  • Rich detail pages with install commands for every major package manager (npm, pnpm, uvx, pip, docker)
  • Faceted search that respects your stack (language, runtime, license, last release)
  • Side-by-side comparison pages for any two MCPs
  • "Alternatives to [X]" pages that rank by reliability, not marketing spend
  • "Best of [category]" rankings, regenerated daily

Try out the Filesystem server, or start with a side-by-side comparison. If you maintain an MCP that's missing, submit it here — free submissions are welcome.

What's next

In the coming months:

  • User reviews with schema.org AggregateRating markup
  • Claim-your-listing flow via GitHub OAuth
  • A paid Verified tier with an audit step — trust badge, dofollow backlink, priority ranking
  • A weekly newsletter of the 5 most-installed new MCPs

Until then, thanks for stopping by. If there's an MCP server missing or a score that looks wrong, the submission form takes 30 seconds.

— The MCPfinder team

Servers mentioned