leakferret vs cobbles

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

MetricleakferretMCP Server cobblesMCP Server

Type: leakferretMCP Server; cobblesMCP Server
Category: leakferretSecurity; cobblesSecurity
GitHub stars: leakferret0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: leakferretNot yet assessed; cobblesNot yet assessed
Community rating: leakferretNo reviews yet; cobblesNo reviews yet
Last commit: leakferretUnknown; cobblesUnknown
Licence: leakferretNone declared; cobblesNone declared
Official: leakferretNo; cobblesNo
Source: leakferret 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.