cve-cache vs Pre-Trip compliance scanner

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

Metriccve-cacheMCP Server Pre-Trip compliance scannerMCP Server

Type: cve-cacheMCP Server; Pre-Trip compliance scannerMCP Server
Category: cve-cacheSecurity; Pre-Trip compliance scannerSecurity
GitHub stars: cve-cache0; Pre-Trip compliance scanner0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: cve-cacheNot yet assessed; Pre-Trip compliance scannerNot yet assessed
Community rating: cve-cacheNo reviews yet; Pre-Trip compliance scannerNo reviews yet
Last commit: cve-cacheUnknown; Pre-Trip compliance scannerUnknown
Licence: cve-cacheNone declared; Pre-Trip compliance scannerNone declared
Official: cve-cacheNo; Pre-Trip compliance scannerNo
Source: cve-cache Repository; Pre-Trip compliance scannerNot available

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.