skill-registry-sync vs iota-mcp

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

Metricskill-registry-syncMCP Server iota-mcpMCP Server

Type: skill-registry-syncMCP Server; iota-mcpMCP Server
Category: skill-registry-syncOther; iota-mcpOther
GitHub stars: skill-registry-sync0; iota-mcp0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: skill-registry-syncNot yet assessed; iota-mcp74/100 · Good
Community rating: skill-registry-syncNo reviews yet; iota-mcpNo reviews yet
Last commit: skill-registry-syncUnknown; iota-mcp76 days ago
Licence: skill-registry-syncNone declared; iota-mcpNOASSERTION
Official: skill-registry-syncNo; iota-mcpNo
Source: skill-registry-sync 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.