Could Have Been Email vs llamanotes

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

MetricCould Have Been EmailMCP Server llamanotesMCP Server

Type: Could Have Been EmailMCP Server; llamanotesMCP Server
Category: Could Have Been EmailCommunication; llamanotesCommunication
GitHub stars: Could Have Been Email0; llamanotes0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: Could Have Been EmailNot yet assessed; llamanotesNot yet assessed
Community rating: Could Have Been EmailNo reviews yet; llamanotesNo reviews yet
Last commit: Could Have Been EmailUnknown; llamanotesUnknown
Licence: Could Have Been EmailNone declared; llamanotesNone declared
Official: Could Have Been EmailNo; llamanotesNo
Source: Could Have Been Email Repository; llamanotesNot 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.