security-controls vs cobbles

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

Metricsecurity-controlsMCP Server cobblesMCP Server

Type: security-controlsMCP Server; cobblesMCP Server
Category: security-controlsSecurity; cobblesSecurity
GitHub stars: security-controls0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: security-controlsNot yet assessed; cobblesNot yet assessed
Community rating: security-controlsNo reviews yet; cobblesNo reviews yet
Last commit: security-controlsUnknown; cobblesUnknown
Licence: security-controlsNone declared; cobblesNone declared
Official: security-controlsNo; cobblesNo
Source: security-controlsNot available; 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.