Prompt Compass vs cobbles

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

MetricPrompt CompassMCP Server cobblesMCP Server

Type: Prompt CompassMCP Server; cobblesMCP Server
Category: Prompt CompassSecurity; cobblesSecurity
GitHub stars: Prompt Compass0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Prompt CompassNot yet assessed; cobblesNot yet assessed
Community rating: Prompt CompassNo reviews yet; cobblesNo reviews yet
Last commit: Prompt CompassUnknown; cobblesUnknown
Licence: Prompt CompassNone declared; cobblesNone declared
Official: Prompt CompassNo; cobblesNo
Source: Prompt Compass 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.