gods-eye-geospatial-mcp vs HAPI Strava MCP Server

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

Metricgods-eye-geospatial-mcpMCP Server HAPI Strava MCP ServerMCP Server

Type: gods-eye-geospatial-mcpMCP Server; HAPI Strava MCP ServerMCP Server
Category: gods-eye-geospatial-mcpLocation; HAPI Strava MCP ServerLocation
GitHub stars: gods-eye-geospatial-mcp0; HAPI Strava MCP Server8
Trust scoreⓘAuditability and maintenance signals — not a security audit.: gods-eye-geospatial-mcpNot yet assessed; HAPI Strava MCP Server79/100 · Good
Community rating: gods-eye-geospatial-mcpNo reviews yet; HAPI Strava MCP ServerNo reviews yet
Last commit: gods-eye-geospatial-mcpUnknown; HAPI Strava MCP Server9 days ago
Licence: gods-eye-geospatial-mcpNone declared; HAPI Strava MCP ServerMIT
Official: gods-eye-geospatial-mcpNo; HAPI Strava MCP ServerNo
Source: gods-eye-geospatial-mcp Repository; HAPI Strava MCP Server 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.