rubric-protocol vs cobbles

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

Metricrubric-protocolMCP Server cobblesMCP Server

Type: rubric-protocolMCP Server; cobblesMCP Server
Category: rubric-protocolSecurity; cobblesSecurity
GitHub stars: rubric-protocol0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: rubric-protocolNot yet assessed; cobblesNot yet assessed
Community rating: rubric-protocolNo reviews yet; cobblesNo reviews yet
Last commit: rubric-protocolUnknown; cobblesUnknown
Licence: rubric-protocolNone declared; cobblesNone declared
Official: rubric-protocolNo; cobblesNo
Source: rubric-protocol 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.