CollectiveSpend-collectivespend-smithery-mcp vs iota-mcp

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 iota-mcpMCP Server

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