Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/chrisdoc/hevy-mcp/node-hevy-mcpgit clone --depth 1 https://github.com/chrisdoc/hevy-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/chrisdoc/hevy-mcp/node-hevy-mcp)<a href="https://agentmods.dev/mcp/chrisdoc/hevy-mcp/node-hevy-mcp"><img src="https://agentmods.dev/badge/mcp/chrisdoc/hevy-mcp/node-hevy-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
hevy-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- hevy-mcp — 100% identical, 0 lines differ
What it actually says
{
"hevy-mcp": {
"command": "npx",
"args": [
"-y",
"hevy-mcp"
],
"env": {
"HEVY_API_KEY": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 12 lines scan A 8ca9daadceee
hevy-mcp is an MCP server published in the GitHub repository chrisdoc/hevy-mcp (451 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
withings
MCP server for Withings health data — sleep, activity, heart, and body metrics. Remote server at withings-mcp.com.
whoopmcp
MCP server "whoopmcp" as configured in kurok/whoopmcp. Runs locally from the whoopmcp Python package. Needs 3 environment variables to run.
macrofactor-mcp
Unofficial local fueling and recovery decision engine; not affiliated with MacroFactor or Stronger By Science; not medical advice. Runs locally from the macrofactor-mcp Python package. Needs 3 environment variables to run.
hevy-coach
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package.
musclesworked
Exercise-to-muscle mapping: 856 exercises, 65 muscles, workout analysis & alternatives. Runs locally from the musclesworked-mcp npm package. Needs 1 environment variable to run.
boostcamp-mcp
MCP server "boostcamp-mcp" as configured in Alex-Keyes/boostcamp-mcp. Runs locally from the boostcamp-mcp Python package.