Pulsedive vs cobbles

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

MetricPulsediveMCP Server cobblesMCP Server

Type: PulsediveMCP Server; cobblesMCP Server
Category: PulsediveSecurity; cobblesSecurity
GitHub stars: Pulsedive0; cobbles0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: PulsediveNot yet assessed; cobblesNot yet assessed
Community rating: PulsediveNo reviews yet; cobblesNo reviews yet
Last commit: PulsediveUnknown; cobblesUnknown
Licence: PulsediveNone declared; cobblesNone declared
Official: PulsediveNo; cobblesNo
Source: Pulsedive 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.