improving-mcp-tools vs test-remediation

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

Metricimproving-mcp-toolsSkill test-remediationSkill

Type: improving-mcp-toolsSkill; test-remediationSkill
Category: improving-mcp-toolsSecurity; test-remediationSecurity
GitHub stars: improving-mcp-tools0; test-remediation0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: improving-mcp-toolsNot yet assessed; test-remediationNot yet assessed
Community rating: improving-mcp-toolsNo reviews yet; test-remediationNo reviews yet
Last commit: improving-mcp-toolsUnknown; test-remediationUnknown
Licence: improving-mcp-toolsNone declared; test-remediationNone declared
Official: improving-mcp-toolsNo; test-remediationNo
Source: improving-mcp-tools Repository; test-remediation 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.