SigRank — Token Efficiency Leaderboard vs cobbles

Side by side on the facts. GitHub figures come straight from each repository; ratings come from signed-in reviewers here.

MetricSigRank — Token Efficiency LeaderboardMCP Server cobblesMCP Server

Type: SigRank — Token Efficiency LeaderboardMCP Server; cobblesMCP Server
Category: SigRank — Token Efficiency LeaderboardSecurity; cobblesSecurity
GitHub stars: SigRank — Token Efficiency Leaderboard0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: SigRank — Token Efficiency LeaderboardNot yet assessed; cobblesNot yet assessed
Community rating: SigRank — Token Efficiency LeaderboardNo reviews yet; cobblesNo reviews yet
Last commit: SigRank — Token Efficiency LeaderboardUnknown; cobblesUnknown
Licence: SigRank — Token Efficiency LeaderboardNone declared; cobblesNone declared
Official: SigRank — Token Efficiency LeaderboardNo; cobblesNo
Source: SigRank — Token Efficiency Leaderboard Repository; cobbles Repository

Highlighted cells win that row on an objective measure. Rows without a clear winner — category, licence, source — are left unmarked. A higher trust score means better auditability and maintenance, not safer code.