updated 2026-10-16 20:06 UTC

Strava MCP

Repository

A Model Context Protocol (MCP) server that connects to Strava API, providing tools to access Strava data through LLMs

MCP Servers TypeScript Listed MIT

Is Strava MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.9 / 10
Provenance None
Signed commits 18%
Last push 125d ago
Advisories None known
Compare Strava MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Strava MCP scores 43.7/100 (Grade D), ranked #1150 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.9/10; 18% of recent commits are signed; no published advisory affects its latest release (strava-mcp-server); last pushed 2026-06-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Strava MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Strava MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/r-huijts/strava-mcp, MIT, last pushed 2026-06-13. 18% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.9/10 (scanned Oct 15, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 0

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: strava-mcp-server 1.2.0. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 3.0/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Strava MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Strava MCP compares in MCP Servers

  1. #659 MCP Ip2location Io 44.0 +0.3
  2. #660 Perplexity Comet MCP 43.8 +0.1
  3. #661 Strava MCP 43.7 this agent
  4. #662 Adaptive Cards MCP 43.5 −0.2
  5. #663 Memory MCP 43.5 −0.2

Bars show each HVTrust score; the tick marks Strava MCP’s 43.7.

Where the 43.7 comes from

HVTrust dimensions vs the MCP Servers average

43.7 / 100 · 100.0% confidence

Strava MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.5 / 25
6.0 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
11.0 / 17
1.3 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
3.7 / 20
8.6 below avg 12.3
AdoptionLog-scaled stars · package downloads
8.7 / 20
1.3 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-14
Rank Moved
Rank dropped 15 spots (#1124 → #1139)
2026-10-09
Rank Moved
Rank dropped 11 spots (#1097 → #1108)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 125 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Strava MCP View MCP Servers Report missing data
33.0
Activity sub-score · out of 100
#661
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-16 20:06 UTC · Repo last pushed 125 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
500
Forks
93
Last Push
2026-06-13
125 days ago
Commits (4 wk)
0
Downloads (7d)
49
npm
HN mentions (30d)
—
Open Issues
8
Rank Change
▼3
was #1147

Analysis

Activity Inputs

33.0 / 100
StarsRepository reach
16.2 / 30
FreshnessLast push recency
7.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.2 / 20

Common questions about Strava MCP

Public trust evidence for Strava MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Strava MCP publish package provenance?
No published build provenance is currently detected for Strava MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Strava MCP have an OpenSSF Scorecard?
Strava MCP has an OpenSSF Scorecard score of 2.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Strava MCP actively maintained?
Slowing down. Last push was 125 days ago — keep an eye on whether activity resumes.
What license does Strava MCP use?
Strava MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Strava MCP's commits signed?
18% of the last 100 commits to Strava MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Strava MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Strava MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-11
Activity Went Stale
No commits for 90 days

Maintain Strava MCP?

For maintainers

HVTrust scores Strava MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 23Listed 2HVTrust 2Scorecard 1Stale 1Delisted 1MCP 1
2026-10-14
Rank Moved
Rank dropped 15 spots (#1124 → #1139)
2026-10-09
Rank Moved
Rank dropped 11 spots (#1097 → #1108)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 144 spots (#1199 → #1055)
2026-09-23
HVTrust Changed
HVTrust up 26.2pts (19.1 → 45.3)
2026-09-22
Newly Listed
First tracked at rank #1199
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 13 spots (#1036 → #1049)
2026-09-12
Rank Moved
Rank dropped 21 spots (#1008 → #1029)
2026-09-11
Activity Went Stale
No commits for 90 days
2026-09-11
Rank Moved
Rank dropped 10 spots (#998 → #1008)
2026-09-09
Rank Moved
Rank dropped 16 spots (#983 → #999)
2026-09-08
Rank Moved
Rank dropped 10 spots (#973 → #983)
2026-09-07
Rank Moved
Rank dropped 34 spots (#939 → #973)
2026-09-06
Rank Moved
Rank dropped 15 spots (#924 → #939)
2026-09-05
Rank Moved
Rank dropped 55 spots (#869 → #924)
2026-09-04
Rank Moved
Rank dropped 29 spots (#840 → #869)
2026-09-03
Rank Moved
Rank dropped 40 spots (#800 → #840)
2026-09-02
Rank Moved
Rank dropped 45 spots (#755 → #800)
2026-09-01
Rank Moved
Rank dropped 29 spots (#726 → #755)
2026-08-31
Rank Moved
Rank dropped 33 spots (#693 → #726)
2026-08-30
Scorecard Added
OSSF Scorecard: 3.0/10
2026-08-30
Rank Moved
Rank rose 325 spots (#1018 → #693)
2026-08-30
HVTrust Changed
HVTrust up 18.2pts (28.7 → 46.9)
2026-08-29
Rank Moved
Rank dropped 51 spots (#967 → #1018)
2026-08-28
Rank Moved
Rank dropped 36 spots (#931 → #967)
2026-08-27
Rank Moved
Rank dropped 25 spots (#906 → #931)
2026-08-26
Rank Moved
Rank dropped 112 spots (#794 → #906)
2026-08-16
Rank Moved
Rank dropped 15 spots (#775 → #790)
2026-08-10
Rank Moved
Rank dropped 41 spots (#730 → #771)
2026-08-08
Newly Listed
First tracked at rank #728
GitHub → npm: strava-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 43.7 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/strava-mcp.svg)](https://hvtracker.net/agents/strava-mcp)
HTML:
<a href="https://hvtracker.net/agents/strava-mcp"><img src="https://hvtracker.net/badge/strava-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON