Pre-Trip compliance scanner vs cobbles

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

MetricPre-Trip compliance scannerMCP Server cobblesMCP Server

Type: Pre-Trip compliance scannerMCP Server; cobblesMCP Server
Category: Pre-Trip compliance scannerSecurity; cobblesSecurity
GitHub stars: Pre-Trip compliance scanner0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Pre-Trip compliance scannerNot yet assessed; cobblesNot yet assessed
Community rating: Pre-Trip compliance scannerNo reviews yet; cobblesNo reviews yet
Last commit: Pre-Trip compliance scannerUnknown; cobblesUnknown
Licence: Pre-Trip compliance scannerNone declared; cobblesNone declared
Official: Pre-Trip compliance scannerNo; cobblesNo
Source: Pre-Trip compliance scannerNot 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.