CollectiveSpend-collectivespend-smithery-mcp vs uselessfacts

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

MetricCollectiveSpend-collectivespend-smithery-mcpMCP Server uselessfactsMCP Server

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