filewash vs cobbles

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

MetricfilewashMCP Server cobblesMCP Server

Type: filewashMCP Server; cobblesMCP Server
Category: filewashSecurity; cobblesSecurity
GitHub stars: filewash0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: filewashNot yet assessed; cobblesNot yet assessed
Community rating: filewashNo reviews yet; cobblesNo reviews yet
Last commit: filewashUnknown; cobblesUnknown
Licence: filewashNone declared; cobblesNone declared
Official: filewashNo; cobblesNo
Source: filewash 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.