Content Provenance vs iota-mcp

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

MetricContent ProvenanceMCP Server iota-mcpMCP Server

Type: Content ProvenanceMCP Server; iota-mcpMCP Server
Category: Content ProvenanceOther; iota-mcpOther
GitHub stars: Content Provenance0; iota-mcp0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Content ProvenanceNot yet assessed; iota-mcp74/100 · Good
Community rating: Content ProvenanceNo reviews yet; iota-mcpNo reviews yet
Last commit: Content ProvenanceUnknown; iota-mcp76 days ago
Licence: Content ProvenanceNone declared; iota-mcpNOASSERTION
Official: Content ProvenanceNo; iota-mcpNo
Source: Content ProvenanceNot 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.