CLIO Chronolog vs gemini-code-context-mcp

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

MetricCLIO ChronologMCP Server gemini-code-context-mcpMCP Server

Type: CLIO ChronologMCP Server; gemini-code-context-mcpMCP Server
Category: CLIO ChronologAI Tools; gemini-code-context-mcpAI Tools
GitHub stars: CLIO Chronolog0; gemini-code-context-mcp0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: CLIO ChronologNot yet assessed; gemini-code-context-mcpNot yet assessed
Community rating: CLIO ChronologNo reviews yet; gemini-code-context-mcpNo reviews yet
Last commit: CLIO ChronologUnknown; gemini-code-context-mcpUnknown
Licence: CLIO ChronologNone declared; gemini-code-context-mcpNone declared
Official: CLIO ChronologNo; gemini-code-context-mcpNo
Source: CLIO Chronolog Repository; gemini-code-context-mcp 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.