Enrich — Company Domain Intelligence vs iota-mcp

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

MetricEnrich — Company Domain IntelligenceMCP Server iota-mcpMCP Server

Type: Enrich — Company Domain IntelligenceMCP Server; iota-mcpMCP Server
Category: Enrich — Company Domain IntelligenceOther; iota-mcpOther
GitHub stars: Enrich — Company Domain Intelligence0; iota-mcp0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Enrich — Company Domain IntelligenceNot yet assessed; iota-mcp74/100 · Good
Community rating: Enrich — Company Domain IntelligenceNo reviews yet; iota-mcpNo reviews yet
Last commit: Enrich — Company Domain IntelligenceUnknown; iota-mcp76 days ago
Licence: Enrich — Company Domain IntelligenceNone declared; iota-mcpNOASSERTION
Official: Enrich — Company Domain IntelligenceNo; iota-mcpNo
Source: Enrich — Company Domain Intelligence 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.