Strava MCP Servers: 9 Implementations Compared

The MCP ecosystem often has several independent packages implementing the same tool — and "Strava" currently has 9. Every one of them was scanned with the same deterministic engine, so the numbers below are directly comparable: the Trust Score (A–F), the capability blast radius, and how much of the package the scan could actually inspect. They are ranked by score; ties break toward unscoped, longer-established packages.

ImplementationPackageTrustCapabilityCoverageFindingsScanned
Stravabest by rmarescu strava-mcp npm A 100/100 Minimal Source 0 2026-07-22
Strava by adrienlupo mcp-strava npm A 100/100 Minimal Source 0 2026-07-22
Strava by keitaro_aigc @keitaro_aigc/strava-mcp-server npm A 100/100 Moderate Source 1 2026-07-22
Strava by r-huijts strava-mcp-server npm A 100/100 Moderate Source 3 2026-07-22
Strava by stugal @stugal/strava-mcp-server npm A 100/100 Moderate Source 3 2026-07-22
Strava by r-huijts @r-huijts/strava-mcp-server npm A 100/100 Moderate Source 3 2026-07-22
Strava by PyPI strava-mcp PyPI A 98/100 Minimal Source 1 2026-07-22
Strava by PyPI mcp-strava PyPI A 98/100 Minimal Source 1 2026-07-22
Strava by tomek-korbak strava-mcp-server PyPI A 98/100 Minimal Source 1 2026-07-22

A higher-ranked implementation is not "the official one" — ranking reflects only what the deterministic scan found in each published package. Open an implementation to read its individual findings with evidence, its scan history per version, and to grab an embeddable badge. Scores are automated opinions, recomputed on every rescan.