luviner vs uselessfacts

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

MetricluvinerMCP Server uselessfactsMCP Server

Type: luvinerMCP Server; uselessfactsMCP Server
Category: luvinerOther; uselessfactsOther
GitHub stars: luviner0; uselessfacts0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: luvinerNot yet assessed; uselessfacts74/100 · Good
Community rating: luvinerNo reviews yet; uselessfactsNo reviews yet
Last commit: luvinerUnknown; uselessfacts58 days ago
Licence: luvinerNone declared; uselessfactsMIT
Official: luvinerNo; uselessfactsNo
Source: luviner Repository; uselessfacts 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.