Loading the page.
Documentation
Journal
Frontend
Backend
Admin
CI/CD
Loading the page.
The ranking covers the full official Model Context Protocol registry pool (registry.modelcontextprotocol.io), with daily automatic updates. The 0–100 score uses only open, verifiable signals; the formula and weights are public, and changing the weights creates a new methodology version.
score = 45×stars + 30×freshness + 15×provenance + 10×completeness; archived repository - final score ×0.5. Ranking: score, ties broken by stars, then name.
Log scale: log10(stars+1)/5, capped at 100k+. Counted only when the repository owner matches the server namespace (anti-star-farming).
Last activity (commit or registry update): ≤30 days - 1.0, ≤90 - 0.7, ≤180 - 0.45, ≤365 - 0.25, older - 0.1.
The official registry namespace is cryptographically verified: MCP project reference servers - 1.0, vendor domain (DNS/HTTP verification) - 0.9, community (io.github.*) - 0.6.
Whether a description, repository, and distribution method (package or hosted remote) are available. Archived repositories halve the final score.
The registry verifies the namespace, but not its link to the repository: a server can specify someone else's popular repository in repository.url. For GitHub namespaces, GitHub signals count only when the repository owner matches the namespace owner. The first pipeline run filtered out 288 such entries.
Code quality, security, the real usefulness of tools, or production suitability. Score is an indicator of popularity, activity, and provenance. Before connecting a server to an agent, perform your own checks: permissions, secrets, network calls. Runtime testing and deeper trust signals are planned for future methodology versions.