StressZero MCP - Burnout Risk Scoring vs iota-mcp

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

MetricStressZero MCP - Burnout Risk ScoringMCP Server iota-mcpMCP Server

Type: StressZero MCP - Burnout Risk ScoringMCP Server; iota-mcpMCP Server
Category: StressZero MCP - Burnout Risk ScoringOther; iota-mcpOther
GitHub stars: StressZero MCP - Burnout Risk Scoring0; iota-mcp0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: StressZero MCP - Burnout Risk ScoringNot yet assessed; iota-mcp74/100 · Good
Community rating: StressZero MCP - Burnout Risk ScoringNo reviews yet; iota-mcpNo reviews yet
Last commit: StressZero MCP - Burnout Risk ScoringUnknown; iota-mcp76 days ago
Licence: StressZero MCP - Burnout Risk ScoringNone declared; iota-mcpNOASSERTION
Official: StressZero MCP - Burnout Risk ScoringNo; iota-mcpNo
Source: StressZero MCP - Burnout Risk Scoring 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.