Default Privacy vs cobbles

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

MetricDefault PrivacyMCP Server cobblesMCP Server

Type: Default PrivacyMCP Server; cobblesMCP Server
Category: Default PrivacySecurity; cobblesSecurity
GitHub stars: Default Privacy0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Default PrivacyNot yet assessed; cobblesNot yet assessed
Community rating: Default PrivacyNo reviews yet; cobblesNo reviews yet
Last commit: Default PrivacyUnknown; cobblesUnknown
Licence: Default PrivacyNone declared; cobblesNone declared
Official: Default PrivacyNo; cobblesNo
Source: Default PrivacyNot 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.