MCP stdio ShellGuard vs uselessfacts

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

MetricMCP stdio ShellGuardMCP Server uselessfactsMCP Server

Type: MCP stdio ShellGuardMCP Server; uselessfactsMCP Server
Category: MCP stdio ShellGuardOther; uselessfactsOther
GitHub stars: MCP stdio ShellGuard0; uselessfacts0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: MCP stdio ShellGuardNot yet assessed; uselessfacts74/100 · Good
Community rating: MCP stdio ShellGuardNo reviews yet; uselessfactsNo reviews yet
Last commit: MCP stdio ShellGuardUnknown; uselessfacts58 days ago
Licence: MCP stdio ShellGuardNone declared; uselessfactsMIT
Official: MCP stdio ShellGuardNo; uselessfactsNo
Source: MCP stdio ShellGuard 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.