K01 Synthetic Health Data vs cobbles

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

MetricK01 Synthetic Health DataMCP Server cobblesMCP Server

Type: K01 Synthetic Health DataMCP Server; cobblesMCP Server
Category: K01 Synthetic Health DataSecurity; cobblesSecurity
GitHub stars: K01 Synthetic Health Data0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: K01 Synthetic Health DataNot yet assessed; cobblesNot yet assessed
Community rating: K01 Synthetic Health DataNo reviews yet; cobblesNo reviews yet
Last commit: K01 Synthetic Health DataUnknown; cobblesUnknown
Licence: K01 Synthetic Health DataNone declared; cobblesNone declared
Official: K01 Synthetic Health DataNo; cobblesNo
Source: K01 Synthetic Health Data 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.