How MCP CLI scored a C.

• code

  33/100
  • ✓ Contributors & bus-factor: 2 recent contributors — concentrated
  • ✓ Commit recency: last commit 215d ago
  • ↓ Commit cadence: 0 commits in 90 days
  • ✓ Issue close ratio: 25% of issues closed
  • ✓ Release cadence: 5 releases in 12 months
  • ✓ Stars (log-damped): 1,270 stars (log-damped)
  • – Star authenticity: star-velocity check unavailable — GitHub no longer publishes stargazer timestamps for this repo
  • – Dependent repos: not measurable — no package listing on a registry we can query

• identity

  Not measured
  • – Identity: not yet active — activates with verified publisher claims

• audits

  Not measured
  • – Third-party scans: not measurable — no registry listings for this tool

• freshness

  74/100
  • ↓ Last shipped: last commit 215d ago — standard-churn tools are expected to ship about every 120d

• community

  53/100
  • – Recommends: no recommends from gate-passing builders yet
  • ✓ Hacker News mentions: 4 Hacker News stories pointing at this tool

Components that could not be measured are left out of the average entirely, and their weight is redistributed, never scored as zero. Identity and Community are left out the same way when they would not have raised the score. How scores are calculated.