API Locker vs cobbles

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

MetricAPI LockerMCP Server cobblesMCP Server

Type: API LockerMCP Server; cobblesMCP Server
Category: API LockerSecurity; cobblesSecurity
GitHub stars: API Locker0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: API LockerNot yet assessed; cobblesNot yet assessed
Community rating: API LockerNo reviews yet; cobblesNo reviews yet
Last commit: API LockerUnknown; cobblesUnknown
Licence: API LockerNone declared; cobblesNone declared
Official: API LockerNo; cobblesNo
Source: API Locker 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.