secure-vault vs cobbles

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

Metricsecure-vaultMCP Server cobblesMCP Server

Type: secure-vaultMCP Server; cobblesMCP Server
Category: secure-vaultSecurity; cobblesSecurity
GitHub stars: secure-vault0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: secure-vaultNot yet assessed; cobblesNot yet assessed
Community rating: secure-vaultNo reviews yet; cobblesNo reviews yet
Last commit: secure-vaultUnknown; cobblesUnknown
Licence: secure-vaultNone declared; cobblesNone declared
Official: secure-vaultNo; cobblesNo
Source: secure-vault 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.