The MCP Server Leaderboard

Top 100 of 14,252 ranked servers shown. Full published dataset: CSV · JSON.

How the ranking works

Each server's score blends three public signals: GitHub stars (60%), npm weekly downloads (25%), and how recently the repository was pushed (15%, on a 45-day half-life). Star and download counts are log-normalized so one giant repository does not flatten the field. Servers come from the official MCP registry. Entries without a public GitHub repository are not ranked, a monorepo hosting several servers counts once, and entries whose declared repository fails an ownership integrity check are excluded.

score = 100 × ( 0.60 · log10(stars+1)/log10(max_stars+1) + 0.25 · log10(downloads+1)/log10(max_downloads+1) + 0.15 · 2^(−days_since_push/45) )

max_stars and max_downloads are the field maxima in each run; servers with no npm package score zero on the downloads term.

Limitations

• Stars and downloads measure popularity, not quality. A well-marketed server will outrank a better-engineered one.
• Download counts come from npm only. Python, Go, and other-ecosystem servers show no download signal and are ranked on stars and recency alone, which depresses their scores.
• A monorepo counts once regardless of how many servers it hosts, so multi-server repositories are under-represented — dozens of servers, one row.
• Ownership integrity checks (the declared repository must verifiably correspond to the registry entry) can exclude legitimate servers with unusual setups, such as forks, mirrors, or repositories renamed after registration.
• Recency weighting favors actively developed servers. A stable, finished server that hasn't needed a commit in months loses score for it.
• Only the top 100 of the ranked field is published. Ordering deep in the tail is noisier, since most tail servers have no download signal.

How do I get my server listed? Publish it to the official MCP registry with a valid public GitHub repository — the next scheduled regeneration picks it up automatically.