code-impact-mcp vs uselessfacts

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

Metriccode-impact-mcpMCP Server uselessfactsMCP Server

Type: code-impact-mcpMCP Server; uselessfactsMCP Server
Category: code-impact-mcpOther; uselessfactsOther
GitHub stars: code-impact-mcp0; uselessfacts0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: code-impact-mcpNot yet assessed; uselessfacts74/100 · Good
Community rating: code-impact-mcpNo reviews yet; uselessfactsNo reviews yet
Last commit: code-impact-mcpUnknown; uselessfacts58 days ago
Licence: code-impact-mcpNone declared; uselessfactsMIT
Official: code-impact-mcpNo; uselessfactsNo
Source: code-impact-mcp 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.