Anamnesis vs enforcement-database

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

MetricAnamnesisMCP Server enforcement-databaseMCP Server

Type: AnamnesisMCP Server; enforcement-databaseMCP Server
Category: AnamnesisDatabases; enforcement-databaseDatabases
GitHub stars: Anamnesis0; enforcement-database0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: AnamnesisNot yet assessed; enforcement-databaseNot yet assessed
Community rating: AnamnesisNo reviews yet; enforcement-databaseNo reviews yet
Last commit: AnamnesisUnknown; enforcement-databaseUnknown
Licence: AnamnesisNone declared; enforcement-databaseNone declared
Official: AnamnesisNo; enforcement-databaseNo
Source: Anamnesis Repository; enforcement-database 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.