SecurityScan vs cobbles

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

MetricSecurityScanMCP Server cobblesMCP Server

Type: SecurityScanMCP Server; cobblesMCP Server
Category: SecurityScanSecurity; cobblesSecurity
GitHub stars: SecurityScan0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: SecurityScanNot yet assessed; cobblesNot yet assessed
Community rating: SecurityScanNo reviews yet; cobblesNo reviews yet
Last commit: SecurityScanUnknown; cobblesUnknown
Licence: SecurityScanNone declared; cobblesNone declared
Official: SecurityScanNo; cobblesNo
Source: SecurityScan 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.