AgentStore Score formula
0.40 × install_score + 0.30 × activity_score + 0.30 × rating_score
Recalculated every Saturday at 00:00 UTC.
How each component works
Actual usage is the most important. We take Smithery calls, npm / PyPI monthly downloads, then normalize.
npm / PyPI monthly × 3 to be comparable to cumulative Smithery calls. log10 smooths the long tail.
Measures maintenance and community engagement.
- · commit_recency: days since last commit, <30d=1.0, >180d=0.0
- · contributors: log10(# contributors) / 2, max 1.0
- · issue_response: median response <48h=1.0
Weighted blend of user reviews and our editors' assessment.
Editor weight dominates below 10 reviews; user ratings take over above that threshold.
The 6 rankings
Anti-gaming measures
- · npm / PyPI downloads filter out CI patterns (regular scheduled pulls don't count)
- · Same-IP burst Smithery calls are rate-limited before counting
- · Anomalies get flagged; proven gaming leads to deranking or removal
How our own tools are handled
AgentStore Studio tools use the same algorithm. They display an "AgentStore Studio" badge for transparency, but receive no score bonus. If an in-house tool tops a ranking, we'll explain why in the data.
Disagree with a ranking?
Open a GitHub issue, or email methodology@agentstore.xyz with the data you're seeing. We respond publicly.