geo-analyzer vs uselessfacts

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

Metricgeo-analyzerMCP Server uselessfactsMCP Server

Type: geo-analyzerMCP Server; uselessfactsMCP Server
Category: geo-analyzerOther; uselessfactsOther
GitHub stars: geo-analyzer0; uselessfacts0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: geo-analyzerNot yet assessed; uselessfacts74/100 · Good
Community rating: geo-analyzerNo reviews yet; uselessfactsNo reviews yet
Last commit: geo-analyzerUnknown; uselessfacts58 days ago
Licence: geo-analyzerNone declared; uselessfactsMIT
Official: geo-analyzerNo; uselessfactsNo
Source: geo-analyzer 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.