A transparent, data-driven approach to evaluating MCP server quality
The Zone Score is our commitment to helping developers make informed decisions. We believe that quality metrics should be open, understandable, and based on objective data that matters to real-world usage.
Every server in our directory receives a Zone Score from 0-100, calculated using publicly available data from [GitHub](https://github.com), [NPM](https://www.npmjs.com), and other sources. We continuously refine our methodology based on community feedback and industry best practices inspired by [NPM's scoring methodology](https://docs.npmjs.com/searching-for-and-choosing-packages-to-download#package-search-ranking-criteria).
Measures community adoption and interest
Evaluates code quality and developer experience
Tracks ongoing development and support
Let's walk through how we calculate the Zone Score for a typical server:
Popularity Metrics
Quality Metrics
Maintenance Metrics
We update Zone Scores daily to reflect the latest metrics from [GitHub API](https://docs.github.com/en/rest) and other sources. This ensures that active development and community engagement are accurately represented.
Absolutely! Focus on maintaining your repository, responding to issues, improving documentation, and fostering community engagement. Every positive action contributes to a better score.
We're continuously expanding our data sources. Currently, we integrate with GitHub for most metrics, with NPM and other platforms coming soon to provide even more comprehensive scoring.
While our methodology is fully transparent and inspired by industry standards like [NPM's package ranking](https://docs.npmjs.com/searching-for-and-choosing-packages-to-download#package-search-ranking-criteria), the implementation details are proprietary to prevent gaming. We believe this balance ensures fairness while maintaining score integrity.
We're committed to making the Zone Score as fair and useful as possible.
Read Our Blog