spec-score-mcp 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.

Metricspec-score-mcpMCP Server gemini-code-context-mcpMCP Server

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