MCP Compliance Preflight vs cobbles

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

MetricMCP Compliance PreflightMCP Server cobblesMCP Server

Type: MCP Compliance PreflightMCP Server; cobblesMCP Server
Category: MCP Compliance PreflightSecurity; cobblesSecurity
GitHub stars: MCP Compliance Preflight0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: MCP Compliance PreflightNot yet assessed; cobblesNot yet assessed
Community rating: MCP Compliance PreflightNo reviews yet; cobblesNo reviews yet
Last commit: MCP Compliance PreflightUnknown; cobblesUnknown
Licence: MCP Compliance PreflightNone declared; cobblesNone declared
Official: MCP Compliance PreflightNo; cobblesNo
Source: MCP Compliance PreflightNot available; 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.