mcp-threatintel vs cobbles

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

Metricmcp-threatintelMCP Server cobblesMCP Server

Type: mcp-threatintelMCP Server; cobblesMCP Server
Category: mcp-threatintelSecurity; cobblesSecurity
GitHub stars: mcp-threatintel0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: mcp-threatintelNot yet assessed; cobblesNot yet assessed
Community rating: mcp-threatintelNo reviews yet; cobblesNo reviews yet
Last commit: mcp-threatintelUnknown; cobblesUnknown
Licence: mcp-threatintelNone declared; cobblesNone declared
Official: mcp-threatintelNo; cobblesNo
Source: mcp-threatintel 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.