Stakeholder Report Publisher vs iota-mcp

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

MetricStakeholder Report PublisherMCP Server iota-mcpMCP Server

Type: Stakeholder Report PublisherMCP Server; iota-mcpMCP Server
Category: Stakeholder Report PublisherOther; iota-mcpOther
GitHub stars: Stakeholder Report Publisher0; iota-mcp0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Stakeholder Report PublisherNot yet assessed; iota-mcp74/100 · Good
Community rating: Stakeholder Report PublisherNo reviews yet; iota-mcpNo reviews yet
Last commit: Stakeholder Report PublisherUnknown; iota-mcp76 days ago
Licence: Stakeholder Report PublisherNone declared; iota-mcpNOASSERTION
Official: Stakeholder Report PublisherNo; iota-mcpNo
Source: Stakeholder Report PublisherNot 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.