Is Strava MCP safe to use?

Strava MCP has an HVTrust score of 45.1/100 (Grade D), ranked #1065 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Strava MCP?

Strava MCP scores 45.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 490 GitHub stars and is categorized under MCP Servers.

Strava MCP

r-huijts/strava-mcp

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 105d ago

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 45.1/100 (Grade D), ranked #1065 of 1325 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; last pushed 2026-06-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Strava MCP compares in MCP Servers

#624 Pty MCP 45.1 ±0
#625 CodeWiki MCP — AI-generated docs for GitHub repos 45.1 ±0
#626 Strava MCP 45.1 this agent
#627 Multi-MCP 45.1 ±0
#628 Adaptive Cards MCP 44.7 −0.4

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

Where the 45.1 comes from

HVTrust dimensions vs the MCP Servers average

45.1 / 100 · 100.0% confidence

Strava MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

4.5 / 25

5.8 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.0 / 17

1.2 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

5.0 / 20

7.0 below avg 12.0

AdoptionLog-scaled stars · package downloads

8.8 / 20

1.6 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

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)

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 105 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

35.6

Activity sub-score · out of 100

#626

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

490

Forks

Last Push

2026-06-13

105 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1064

Analysis

Activity Inputs

35.6 / 100

StarsRepository reach

16.1 / 30

FreshnessLast push recency

10.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

9.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.9 / 10

OpenSSF Scorecard · scanned Sep 16, 2026

Signed Commits

18%

of last 100 commits verified

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

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 105 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

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

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.3 · Raw JSON