Palimpsest — censorship observatory 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.

MetricPalimpsest — censorship observatoryMCP Server Pre-Trip compliance scannerMCP Server

Type: Palimpsest — censorship observatoryMCP Server; Pre-Trip compliance scannerMCP Server
Category: Palimpsest — censorship observatorySecurity; Pre-Trip compliance scannerSecurity
GitHub stars: Palimpsest — censorship observatory0; Pre-Trip compliance scanner0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Palimpsest — censorship observatoryNot yet assessed; Pre-Trip compliance scannerNot yet assessed
Community rating: Palimpsest — censorship observatoryNo reviews yet; Pre-Trip compliance scannerNo reviews yet
Last commit: Palimpsest — censorship observatoryUnknown; Pre-Trip compliance scannerUnknown
Licence: Palimpsest — censorship observatoryNone declared; Pre-Trip compliance scannerNone declared
Official: Palimpsest — censorship observatoryNo; Pre-Trip compliance scannerNo
Source: Palimpsest — censorship observatory 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.