18,656+ discovery records
1. Index the ecosystem
Public directories and registries help MCP Rank see the market, but indexed records stay separate from recommendations.
Trust roadmap
MCP Rank is building a trust loop, not a scraped leaderboard.
The market only matters if teams, maintainers, and tool builders can use MCP Rank to reduce uncertainty before a server gets installed into a repo, browser, database, cloud account, or customer workspace.
22 source reviewed
2. Check public evidence
Source review checks repository, package, docs, and provenance signals without pretending that public metadata is maintainer confirmation.
20 deep reviewed
3. Deep review risky surfaces
Deep reviews focus on install paths, auth behavior, write actions, local access, data movement, and operational blast radius.
0 maintainer verified
4. Confirm with maintainers
Maintainer Verified stays rare until a maintainer explicitly confirms listing details and MCP Rank records the evidence.
What makes this worth pursuing?
A growing protocol surface
MCP servers now touch sensitive systems: code, local files, SaaS workspaces, payments, browsers, analytics, and cloud infrastructure.
A messy discovery layer
Directories are useful, but broken links, endpoint-only listings, stale metadata, and copied badges make install decisions harder.
A clear wedge
MCP Rank can win by being strict about evidence, transparent about uncertainty, and useful to maintainers who want listings corrected.
Next product milestone
Convert the first maintainer replies into visible corrections, then publish a follow-up report that shows MCP Rank can improve the ecosystem rather than only criticize it.
Next acquisition signal
Earn public references from maintainers, security builders, or MCP directory operators. Acquirers care less about raw rows and more about trust, distribution, and correction workflow ownership.