vuln-intel vs cobbles

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

Metricvuln-intelMCP Server cobblesMCP Server

Type: vuln-intelMCP Server; cobblesMCP Server
Category: vuln-intelSecurity; cobblesSecurity
GitHub stars: vuln-intel0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: vuln-intelNot yet assessed; cobblesNot yet assessed
Community rating: vuln-intelNo reviews yet; cobblesNo reviews yet
Last commit: vuln-intelUnknown; cobblesUnknown
Licence: vuln-intelNone declared; cobblesNone declared
Official: vuln-intelNo; cobblesNo
Source: vuln-intel 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.