Get on Board vs cobbles

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

MetricGet on BoardMCP Server cobblesMCP Server

Type: Get on BoardMCP Server; cobblesMCP Server
Category: Get on BoardSecurity; cobblesSecurity
GitHub stars: Get on Board0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Get on BoardNot yet assessed; cobblesNot yet assessed
Community rating: Get on BoardNo reviews yet; cobblesNo reviews yet
Last commit: Get on BoardUnknown; cobblesUnknown
Licence: Get on BoardNone declared; cobblesNone declared
Official: Get on BoardNo; cobblesNo
Source: Get on BoardNot 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.