sanctions-screening vs cobbles

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

Metricsanctions-screeningMCP Server cobblesMCP Server

Type: sanctions-screeningMCP Server; cobblesMCP Server
Category: sanctions-screeningSecurity; cobblesSecurity
GitHub stars: sanctions-screening0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: sanctions-screeningNot yet assessed; cobblesNot yet assessed
Community rating: sanctions-screeningNo reviews yet; cobblesNo reviews yet
Last commit: sanctions-screeningUnknown; cobblesUnknown
Licence: sanctions-screeningNone declared; cobblesNone declared
Official: sanctions-screeningNo; cobblesNo
Source: sanctions-screening 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.