Httpstatus vs uselessfacts

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

MetricHttpstatusMCP Server uselessfactsMCP Server

Type: HttpstatusMCP Server; uselessfactsMCP Server
Category: HttpstatusOther; uselessfactsOther
GitHub stars: Httpstatus0; uselessfacts0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: HttpstatusNot yet assessed; uselessfacts74/100 · Good
Community rating: HttpstatusNo reviews yet; uselessfactsNo reviews yet
Last commit: HttpstatusUnknown; uselessfacts58 days ago
Licence: HttpstatusNone declared; uselessfactsMIT
Official: HttpstatusNo; uselessfactsNo
Source: Httpstatus 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.