kcp-harness — KCP compliance proxy vs cobbles

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

Metrickcp-harness — KCP compliance proxyMCP Server cobblesMCP Server

Type: kcp-harness — KCP compliance proxyMCP Server; cobblesMCP Server
Category: kcp-harness — KCP compliance proxySecurity; cobblesSecurity
GitHub stars: kcp-harness — KCP compliance proxy0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: kcp-harness — KCP compliance proxyNot yet assessed; cobblesNot yet assessed
Community rating: kcp-harness — KCP compliance proxyNo reviews yet; cobblesNo reviews yet
Last commit: kcp-harness — KCP compliance proxyUnknown; cobblesUnknown
Licence: kcp-harness — KCP compliance proxyNone declared; cobblesNone declared
Official: kcp-harness — KCP compliance proxyNo; cobblesNo
Source: kcp-harness — KCP compliance proxy 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.