Breach402 Owner Protection vs iota-mcp

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

MetricBreach402 Owner ProtectionMCP Server iota-mcpMCP Server

Type: Breach402 Owner ProtectionMCP Server; iota-mcpMCP Server
Category: Breach402 Owner ProtectionOther; iota-mcpOther
GitHub stars: Breach402 Owner Protection0; iota-mcp0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Breach402 Owner ProtectionNot yet assessed; iota-mcp74/100 · Good
Community rating: Breach402 Owner ProtectionNo reviews yet; iota-mcpNo reviews yet
Last commit: Breach402 Owner ProtectionUnknown; iota-mcp76 days ago
Licence: Breach402 Owner ProtectionNone declared; iota-mcpNOASSERTION
Official: Breach402 Owner ProtectionNo; iota-mcpNo
Source: Breach402 Owner ProtectionNot 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.