mcp-token-optimizer 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.

Metricmcp-token-optimizerMCP Server gemini-code-context-mcpMCP Server

Type: mcp-token-optimizerMCP Server; gemini-code-context-mcpMCP Server
Category: mcp-token-optimizerAI Tools; gemini-code-context-mcpAI Tools
GitHub stars: mcp-token-optimizer0; gemini-code-context-mcp0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: mcp-token-optimizerNot yet assessed; gemini-code-context-mcpNot yet assessed
Community rating: mcp-token-optimizerNo reviews yet; gemini-code-context-mcpNo reviews yet
Last commit: mcp-token-optimizerUnknown; gemini-code-context-mcpUnknown
Licence: mcp-token-optimizerNone declared; gemini-code-context-mcpNone declared
Official: mcp-token-optimizerNo; gemini-code-context-mcpNo
Source: mcp-token-optimizer 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.