qc-validator vs iota-mcp

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

Metricqc-validatorMCP Server iota-mcpMCP Server

Type: qc-validatorMCP Server; iota-mcpMCP Server
Category: qc-validatorOther; iota-mcpOther
GitHub stars: qc-validator0; iota-mcp0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: qc-validatorNot yet assessed; iota-mcp74/100 · Good
Community rating: qc-validatorNo reviews yet; iota-mcpNo reviews yet
Last commit: qc-validatorUnknown; iota-mcp76 days ago
Licence: qc-validatorNone declared; iota-mcpNOASSERTION
Official: qc-validatorNo; iota-mcpNo
Source: qc-validator 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.