Hevy MCP Server
Manage your Hevy workouts, routines, folders, and exercise templates. Create and update sessions faster, organize plans, and search exercises to build workouts quickly. Stay synced with changes so your training log is always up to date.
Is Hevy MCP Server safe? Strong public trust posture, backed by multiple independent signals.
Compare Hevy MCP Server
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Hevy MCP Server scores 87.7/100 (Grade A), ranked #43 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.1/10; 100% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Hevy MCP Server compares in MCP Servers
- #8 Apify MCP Server 88.2 +0.5
- #9 ARC-1 88.1 +0.4
- #10 Hevy MCP Server 87.7 this agent
- #11 MCP Hangar 87.4 −0.3
- #12 Canvas MCP 87.4 −0.3
Bars show each HVTrust score; the tick marks Hevy MCP Server’s 87.7.
Where the 87.7 comes from
HVTrust dimensions vs the MCP Servers average
87.7 / 100 · 100.0% confidenceHevy MCP Server MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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
Activity & Reach
Analysis
Activity Inputs
74.2 / 100Supply Chain Trust
Common questions about Hevy MCP Server
Does Hevy MCP Server publish package provenance?
Does Hevy MCP Server have an OpenSSF Scorecard?
Is Hevy MCP Server actively maintained?
What license does Hevy MCP Server use?
Are Hevy MCP Server's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Hevy MCP Server'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.
Maintain Hevy MCP Server?
For maintainers
HVTrust scores Hevy MCP Server 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/hevy-mcp-server)
<a href="https://hvtracker.net/agents/hevy-mcp-server"><img src="https://hvtracker.net/badge/hevy-mcp-server.svg" alt="HVTrust"></a>
Other agents in MCP Servers
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