Skills/npm/hevy-mcp

hevy-mcp@6.2.5

VERIFIED· not started

Publisher claims: "A Model Context Protocol (MCP) server implementation that interfaces with the Hevy fitness tracking app and its API." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher chrisdoc · publishing for 600 daysInstalls 14,080Last detonated 32 min ago
$claude mcp add hevy-mcp -- npx -y hevy-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
API_KEY_VALIDATION_WARNINGHEVY_API_KEYHTTP_BEARER_TOKENOTEL_COLLECTOR_TOKENSENTRY_DSNConfiguration, not credentials: HEVY_MCP_API_TIMEOUT, HEVY_MCP_DEBUG, HEVY_MCP_TELEMETRY, HEVY_MCP_TELEMETRY_DIAGNOSTICS, SENTRY_ENVIRONMENT, SENTRY_RELEASE
Where it talks to
hevyapp.com, hevy.com, hevy-mcp.dev (its own)Also tsdown.dev, kubb.dev, chrisdoc.dev — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names tsdown.dev, kubb.dev, chrisdoc.dev as well as its own vendor. The guard injects API_KEY_VALIDATION_WARNING, HEVY_API_KEY, HTTP_BEARER_TOKEN, OTEL_COLLECTOR_TOKEN, SENTRY_DSN only into requests to hevyapp.com (and its subdomains) and refuses the rest.

$vet-skills run --secrets API_KEY_VALIDATION_WARNING=hevyapp.com,HEVY_API_KEY=hevyapp.com,HTTP_BEARER_TOKEN=hevyapp.com,OTEL_COLLECTOR_TOKEN=hevyapp.com,SENTRY_DSN=hevyapp.com -- npx -y hevy-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 6.2.4

vet-skills diff hevy-mcp 6.2.4 6.2.5

In the sandbox, this version reached for nothing 6.2.4 did not. Compared from the two recorded runs, not from source.

6.2.4 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-16 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 2 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
2.0sprocessdependency install exit 1 · npm error For a full report see: npm error /tmp/ks-detonate-2X6MoJ/task/home/.npm/_logs/2026-11-16T05_16_51_203Z-eresolve-report.txt npm error A complete log of this run can be found in: /tmp/ks-detonate-2X6MoJ/task/home/.npm/_logs/2026-11-16T05_16_51_203Z-debug-0.log
2.0sclaimednot started: dependency install failed (exit 1); the server itself was not observed
2.0sprocessscript backend runs setup only
2.0sprocessno install scripts to re-run

Static findings

HIGH
Hidden zero-width characters detecteddist/runtime-VpGsVyvD.mjs:1768 · Hidden zero-width characters detected — may conceal contentconst UTF8_BOM = "";Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST07
MEDIUM
npx invocation of non-well-known packagedist/runtime-VpGsVyvD.mjs:2821 · npx invocation of non-well-known package — may execute untrusted code" HEVY_API_KEY=your-key npx hevy-mcp --transport http --port 3000"Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/runtime-VpGsVyvD.mjs:2820 · npx invocation of non-well-known package — may execute untrusted code" HEVY_API_KEY=your-key npx hevy-mcp",Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
MCP server using network transport (SSE/HTTP)dist/runtime-VpGsVyvD.mjs:11 · MCP server using network transport (SSE/HTTP) — data sent over network…t, g as metricEndpointIdentity, h as diagnosticEndpointIdentity, i as createHevyMcpServer, l as sanitizeDiagnosticText$1, m as SAFE_OBSERVATION_CODES, n as assertApiKey, o as USER_HASH_CONTEXT, p as createHevyClient, r as parseConfig, s as…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)dist/index.mjs:4 · MCP server using network transport (SSE/HTTP) — data sent over networkimport { i as createHevyMcpServer, n as assertApiKey, p as createHevyClient } from "./config-CHTMUBOx.mjs";Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)dist/config-CHTMUBOx.mjs:7634 · MCP server using network transport (SSE/HTTP) — data sent over network…t as f, metricEndpointIdentity as g, diagnosticEndpointIdentity as h, createHevyMcpServer as i, sanitizeDiagnosticText as l, SAFE_OBSERVATION_CODES as m, assertApiKey as n, USER_HASH_CONTEXT as o, createHevyClient as p, parseConfig as r, c…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04

Cost to the agent

Instructions loaded
≈63 tok
1 file · 10 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.