cve-cache vs cobbles

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

Metriccve-cacheMCP Server cobblesMCP Server

Type: cve-cacheMCP Server; cobblesMCP Server
Category: cve-cacheSecurity; cobblesSecurity
GitHub stars: cve-cache0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: cve-cacheNot yet assessed; cobblesNot yet assessed
Community rating: cve-cacheNo reviews yet; cobblesNo reviews yet
Last commit: cve-cacheUnknown; cobblesUnknown
Licence: cve-cacheNone declared; cobblesNone declared
Official: cve-cacheNo; cobblesNo
Source: cve-cache 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.