vibecheck-mcp vs cobbles

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

Metricvibecheck-mcpMCP Server cobblesMCP Server

Type: vibecheck-mcpMCP Server; cobblesMCP Server
Category: vibecheck-mcpSecurity; cobblesSecurity
GitHub stars: vibecheck-mcp0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: vibecheck-mcpNot yet assessed; cobblesNot yet assessed
Community rating: vibecheck-mcpNo reviews yet; cobblesNo reviews yet
Last commit: vibecheck-mcpUnknown; cobblesUnknown
Licence: vibecheck-mcpNone declared; cobblesNone declared
Official: vibecheck-mcpNo; cobblesNo
Source: vibecheck-mcp Repository; cobbles 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.