Passive Aggression vs uselessfacts

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

MetricPassive AggressionMCP Server uselessfactsMCP Server

Type: Passive AggressionMCP Server; uselessfactsMCP Server
Category: Passive AggressionOther; uselessfactsOther
GitHub stars: Passive Aggression0; uselessfacts0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Passive AggressionNot yet assessed; uselessfacts74/100 · Good
Community rating: Passive AggressionNo reviews yet; uselessfactsNo reviews yet
Last commit: Passive AggressionUnknown; uselessfacts58 days ago
Licence: Passive AggressionNone declared; uselessfactsMIT
Official: Passive AggressionNo; uselessfactsNo
Source: Passive Aggression Repository; uselessfacts 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.