vsafe-risk vs cobbles

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

Metricvsafe-riskMCP Server cobblesMCP Server

Type: vsafe-riskMCP Server; cobblesMCP Server
Category: vsafe-riskSecurity; cobblesSecurity
GitHub stars: vsafe-risk0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: vsafe-riskNot yet assessed; cobblesNot yet assessed
Community rating: vsafe-riskNo reviews yet; cobblesNo reviews yet
Last commit: vsafe-riskUnknown; cobblesUnknown
Licence: vsafe-riskNone declared; cobblesNone declared
Official: vsafe-riskNo; cobblesNo
Source: vsafe-riskNot 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.