hevy-mcp (chrisdoc/hevy-mcp) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 1 tool. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Emerging
89/100
1 month ago

hevy-mcp

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.

→ chrisdoc/hevy-mcp· listed on github_topic

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

chrisdoc

Source: github_topic · also listed on PulseMCP, modelscope

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHubPulseMCPmodelscope

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 4 credentials: CODECOV_TOKEN, HEVY_API_KEY, HEVY_MCP_HTTP_BEARER_TOKEN, OTEL_COLLECTOR_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretCODECOV_TOKEN
🔐 secretHEVY_API_KEYexport =your-hevy-api-key
configHEVY_MCP_API_TIMEOUT30000 ms Local stdio Positive Hevy API timeout in milliseconds. Invalid values fall back to 30 seconds.
configHEVY_MCP_BUILD_MODE
configHEVY_MCP_DEBUGDisabled Local Node Set to exactly 1 for privacy-bounded diagnostics on stderr. Stdout remains reserved for MCP JSON-RPC.
🔐 secretHEVY_MCP_HTTP_BEARER_TOKENNone Non-loopback HTTP Required when --host is not loopback; use a separate token, never the Hevy API key.
configHEVY_MCP_RELEASE
configHEVY_MCP_TELEMETRY0 before startup or import to disable all project
🔐 secretOTEL_COLLECTOR_TOKENprecedence over SENTRY_DSN and packaged or runtime
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deploySENTRY_AUTH_TOKEN
deploySENTRY_DSN
deploySENTRY_ORG
deploySENTRY_PROJECT
deploySENTRY_RELEASE
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

1/1 tools missing one or more hints — mock-tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

Only 0/1 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/1 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/chrisdoc/hevy-mcp)](https://m8ven.ai/mcp/chrisdoc/hevy-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 98a79fe3670f673a3fd8ed1c3123624a16ea3b5f
code hash: 428490fe4463da0c954d5d5d0602e52c1ec2d6c15a6f8fbfd59dfb80fe070dbf
verified: 8/7/2026, 2:14:23 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client