constraints-registry 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.

Metricconstraints-registryMCP Server Pre-Trip compliance scannerMCP Server

Type: constraints-registryMCP Server; Pre-Trip compliance scannerMCP Server
Category: constraints-registrySecurity; Pre-Trip compliance scannerSecurity
GitHub stars: constraints-registry0; Pre-Trip compliance scanner0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: constraints-registryNot yet assessed; Pre-Trip compliance scannerNot yet assessed
Community rating: constraints-registryNo reviews yet; Pre-Trip compliance scannerNo reviews yet
Last commit: constraints-registryUnknown; Pre-Trip compliance scannerUnknown
Licence: constraints-registryNone declared; Pre-Trip compliance scannerNone declared
Official: constraints-registryNo; Pre-Trip compliance scannerNo
Source: constraints-registry 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.