bouncer vs cobbles

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

MetricbouncerMCP Server cobblesMCP Server

Type: bouncerMCP Server; cobblesMCP Server
Category: bouncerSecurity; cobblesSecurity
GitHub stars: bouncer0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: bouncerNot yet assessed; cobblesNot yet assessed
Community rating: bouncerNo reviews yet; cobblesNo reviews yet
Last commit: bouncerUnknown; cobblesUnknown
Licence: bouncerNone declared; cobblesNone declared
Official: bouncerNo; cobblesNo
Source: bouncer 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.