BlackDome Threat Intel vs cobbles

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

MetricBlackDome Threat IntelMCP Server cobblesMCP Server

Type: BlackDome Threat IntelMCP Server; cobblesMCP Server
Category: BlackDome Threat IntelSecurity; cobblesSecurity
GitHub stars: BlackDome Threat Intel0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: BlackDome Threat IntelNot yet assessed; cobblesNot yet assessed
Community rating: BlackDome Threat IntelNo reviews yet; cobblesNo reviews yet
Last commit: BlackDome Threat IntelUnknown; cobblesUnknown
Licence: BlackDome Threat IntelNone declared; cobblesNone declared
Official: BlackDome Threat IntelNo; cobblesNo
Source: BlackDome Threat 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.