TrustAgent — counterparty verification vs cobbles

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

MetricTrustAgent — counterparty verificationMCP Server cobblesMCP Server

Type: TrustAgent — counterparty verificationMCP Server; cobblesMCP Server
Category: TrustAgent — counterparty verificationSecurity; cobblesSecurity
GitHub stars: TrustAgent — counterparty verification0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: TrustAgent — counterparty verificationNot yet assessed; cobblesNot yet assessed
Community rating: TrustAgent — counterparty verificationNo reviews yet; cobblesNo reviews yet
Last commit: TrustAgent — counterparty verificationUnknown; cobblesUnknown
Licence: TrustAgent — counterparty verificationNone declared; cobblesNone declared
Official: TrustAgent — counterparty verificationNo; cobblesNo
Source: TrustAgent — counterparty verification 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.