Vendor Legit Check vs uselessfacts

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

MetricVendor Legit CheckMCP Server uselessfactsMCP Server

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