mcp-reverse-engineering vs uselessfacts

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

Metricmcp-reverse-engineeringMCP Server uselessfactsMCP Server

Type: mcp-reverse-engineeringMCP Server; uselessfactsMCP Server
Category: mcp-reverse-engineeringOther; uselessfactsOther
GitHub stars: mcp-reverse-engineering0; uselessfacts0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: mcp-reverse-engineeringNot yet assessed; uselessfacts74/100 · Good
Community rating: mcp-reverse-engineeringNo reviews yet; uselessfactsNo reviews yet
Last commit: mcp-reverse-engineeringUnknown; uselessfacts58 days ago
Licence: mcp-reverse-engineeringNone declared; uselessfactsMIT
Official: mcp-reverse-engineeringNo; uselessfactsNo
Source: mcp-reverse-engineering 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.