MVR API - Minimum Viable Relationships vs uselessfacts

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

MetricMVR API - Minimum Viable RelationshipsMCP Server uselessfactsMCP Server

Type: MVR API - Minimum Viable RelationshipsMCP Server; uselessfactsMCP Server
Category: MVR API - Minimum Viable RelationshipsOther; uselessfactsOther
GitHub stars: MVR API - Minimum Viable Relationships0; uselessfacts0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: MVR API - Minimum Viable RelationshipsNot yet assessed; uselessfacts74/100 · Good
Community rating: MVR API - Minimum Viable RelationshipsNo reviews yet; uselessfactsNo reviews yet
Last commit: MVR API - Minimum Viable RelationshipsUnknown; uselessfacts58 days ago
Licence: MVR API - Minimum Viable RelationshipsNone declared; uselessfactsMIT
Official: MVR API - Minimum Viable RelationshipsNo; uselessfactsNo
Source: MVR API - Minimum Viable Relationships 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.