jekakos-mcp-user-data-enrichment vs iota-mcp

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

Metricjekakos-mcp-user-data-enrichmentMCP Server iota-mcpMCP Server

Type: jekakos-mcp-user-data-enrichmentMCP Server; iota-mcpMCP Server
Category: jekakos-mcp-user-data-enrichmentOther; iota-mcpOther
GitHub stars: jekakos-mcp-user-data-enrichment0; iota-mcp0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: jekakos-mcp-user-data-enrichment57/100 · Fair; iota-mcp74/100 · Good
Community rating: jekakos-mcp-user-data-enrichmentNo reviews yet; iota-mcpNo reviews yet
Last commit: jekakos-mcp-user-data-enrichment302 days ago; iota-mcp76 days ago
Licence: jekakos-mcp-user-data-enrichmentNone declared; iota-mcpNOASSERTION
Official: jekakos-mcp-user-data-enrichmentNo; iota-mcpNo
Source: jekakos-mcp-user-data-enrichment Repository; 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.