Purify Security Feeds vs cobbles

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

MetricPurify Security FeedsMCP Server cobblesMCP Server

Type: Purify Security FeedsMCP Server; cobblesMCP Server
Category: Purify Security FeedsSecurity; cobblesSecurity
GitHub stars: Purify Security Feeds0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Purify Security FeedsNot yet assessed; cobblesNot yet assessed
Community rating: Purify Security FeedsNo reviews yet; cobblesNo reviews yet
Last commit: Purify Security FeedsUnknown; cobblesUnknown
Licence: Purify Security FeedsNone declared; cobblesNone declared
Official: Purify Security FeedsNo; cobblesNo
Source: Purify Security Feeds 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.