Hevy MCP: why it is not safe to use
We found the hosted Hevy MCP routes your Hevy API key and workout data through a third-party Cloudflare endpoint, which adds privacy exposure.
What we found
Our review did not find hidden instructions, hardcoded secrets, obfuscation, privilege escalation, or undisclosed fetch-and-execute behavior in this repo. The documented behavior is generally clear, and the tool does not expose delete capability. It also documents approval for mutation tools where supported.
The main issue we found is in the optional hosted mode. In that setup, your Hevy API key and workout data are sent to the maintainer's Cloudflare-hosted MCP endpoint before being forwarded to Hevy. This routing is disclosed in the documentation, but it still creates a third-party path for sensitive fitness data and credentials. For users who want to limit where workout history and API keys transit, that extra hop changes the privacy profile compared with a direct local connection.
What to do instead
If you want to use this skill with lower privacy exposure, prefer a self-hosted or local setup so your Hevy API key and workout data are not proxied through the hosted MCP service. Review the README to confirm which mode you are using, and avoid the hosted endpoint if you are not comfortable sending fitness data through a third-party service.
Source: https://github.com/chrisdoc/hevy-mcp
We report what our security review found at the time we checked, with the goal of keeping people safe. Projects change; if a maintainer has since fixed this, we are glad to recheck it. Email hello@agentpod.com.