BadRooBot-my_test_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.

MetricBadRooBot-my_test_mcpMCP Server gemini-code-context-mcpMCP Server

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