Well-Being Check vs uselessfacts

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

MetricWell-Being CheckMCP Server uselessfactsMCP Server

Type: Well-Being CheckMCP Server; uselessfactsMCP Server
Category: Well-Being CheckOther; uselessfactsOther
GitHub stars: Well-Being Check0; uselessfacts0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Well-Being CheckNot yet assessed; uselessfacts74/100 · Good
Community rating: Well-Being CheckNo reviews yet; uselessfactsNo reviews yet
Last commit: Well-Being CheckUnknown; uselessfacts58 days ago
Licence: Well-Being CheckNone declared; uselessfactsMIT
Official: Well-Being CheckNo; uselessfactsNo
Source: Well-Being Check 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.