JSON Contracts 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.

MetricJSON ContractsMCP Server gemini-code-context-mcpMCP Server

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