ClawPipe vs cobbles

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

MetricClawPipeMCP Server cobblesMCP Server

Type: ClawPipeMCP Server; cobblesMCP Server
Category: ClawPipeSecurity; cobblesSecurity
GitHub stars: ClawPipe0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: ClawPipeNot yet assessed; cobblesNot yet assessed
Community rating: ClawPipeNo reviews yet; cobblesNo reviews yet
Last commit: ClawPipeUnknown; cobblesUnknown
Licence: ClawPipeNone declared; cobblesNone declared
Official: ClawPipeNo; cobblesNo
Source: ClawPipe 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.