MCP servers › io.github.almostjacked › hevy-mcp

MCP server · registry snapshot 2026-10-04 · last tested 2026-10-08

io.github.almostjacked/hevy-mcp

Create Hevy routines and analyze your training from chat. Unofficial; BYO Hevy PRO API key. — the publisher's description

Topic: science-health-and-education · AI-classifiedversion 0.1.0TypeScriptMITstandard input/output, streamable HTTP

Summary

io.github.almostjacked/hevy-mcp is a remote and local MCP server listed in the official MCP registry at version 0.1.0. On 2026-10-08 it required sign-in before listing anything, so we could not read its inventory. We never use a credential its operator did not give us. 1 of the 18 checks that apply to it was exercised. Results of the checks are published only after we have verified them and told the publisher.

Needs the operator's credential

The server requires sign-in. We never use a credential its operator did not give us, so most checks could not run. No security score is given; a check we did not run is never counted as passed.

Key facts

Runs: remote and local package
Transport: standard input/output, streamable HTTP
Sign-in: required
Package: npm · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Topic: science-health-and-educationAI-classified
Last tested: 2026-10-08

The 18 checks at a glanceour test · 2026-10-08

Inventory: not run · needs the operator's credential
Hidden instructions: not run · needs the operator's credential
Real execution: not run · needs the operator's credential
Secret leak: not run · needs the operator's credential
Internal addresses: not run · needs the operator's credential
Unconfirmed changes: not run · needs the operator's credential
Bad input: not run · needs the operator's credential
Model requests: not run · needs the operator's credential
Sensitive questions: not run · needs the operator's credential
Folder boundary: not run · needs the operator's credential
Log leaks: not run · needs the operator's credential
Hidden content: not run · needs the operator's credential
Fake assistant turns: not run · needs the operator's credential
Token passthrough: not run · needs the operator's credential
Token audience: not run · needs the operator's credential
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

1 exercised17 not run (reason given)0 not applicable

How fresh this is

Live-tested: attempted, see below
Last tested: 2026-10-08
Registry data: snapshot 2026-10-04
Package and repository: checked 2026-10-06
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 1 of the 18 checks that apply to it was exercised. Results of the checks are published only after we have verified them and told the publisher.

Exercised · 1

18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 17

1Inventory
tool-listReads the declared tools, resources and prompts.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
3Real execution
real-executionCalls a tool and checks what really happens.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
7Bad input
error-handlingSends bad input and watches how the server answers.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
8Model requests
samplingChecks whether the server asks the client's model to act for it.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
12Hidden content
audience-hidingChecks resources that hide content from the user.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.Needs a real token issued by the server's own sign-in service, which only its operator can give us.not run · needs the operator's credential
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.Needs a real token issued by the server's own sign-in service, which only its operator can give us.not run · needs the operator's credential
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do without their authorization.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Source: our own test, 2026-10-08, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model. This server also has a package test (0 of 18 applicable checks exercised).

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a session with the server's remote endpoint
The server asked for sign-in before listing anything.
1,037 msFinished: 1 check exercised.

What it is

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint hevy-coach.ajwallacemusic.workers.dev/mcp	Endpoint answered and asked for sign-in	matches	our test · 2026-10-08
No credential declared as required	Required sign-in	differs	our test · 2026-10-08
Published package can be started	Started, but no session could be opened	no session	our test · 2026-10-09
Version 0.1.0 on npm	Exists and can be installed	matches	npm · 2026-10-06
Repository github.com/almostjacked/hevy-mcp	Opens publicly	matches	api.github.com · 2026-10-06

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.1.0
Latest stable: 0.1.0
Status: current
Withdrawn: no

Source: registry.npmjs.org · 2026-10-06. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-08 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-FbcdSYJ22BX7Kpc9a…
Signature: signed
License: MIT

Source: the package registry · 2026-10-06.

Usage

Downloads: 168 in the last month

Source: api.npmjs.org · 2026-10-06.

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.almostjacked
GitHub owner: an organization (almostjacked)
Build record: signed

Repository: github.com/almostjacked/hevy-mcp
Stars: 0
Repository age: 31–90 days
Last push: 31–90 days ago
Archived: no

Source: the registry entry and api.github.com · 2026-10-06.

Choosing

Common questions about io.github.almostjacked/hevy-mcp

Answered from the data above

Does io.github.almostjacked/hevy-mcp need an API key or sign-in?

It required sign-in on 2026-10-08. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.almostjacked/hevy-mcp been security tested?

Partly. 1 of the 18 checks that apply to it was exercised. The server requires sign-in. We never use a credential its operator did not give us, so most checks could not run. No security verdict is published before verification.

Is the listed version current?

Yes. The registry lists 0.1.0, the latest stable release on npm.

Where is the source code of io.github.almostjacked/hevy-mcp?

In github.com/almostjacked/hevy-mcp, which opens publicly.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

science-health-and-education

AI-classified · 2026-10-08

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

TypeScript

api.github.com · 2026-10-08

Hosting type

remote and local package

registry · 2026-10-04

MCP capability

not checked

not read (no session)

Transport

standard input/output, streamable HTTP

registry · 2026-10-04

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-04

Freshness

31–90 days

registry updatedAt · 2026-10-04

Lifecycle status

active

registry · 2026-10-04

License class

permissive

package registry · 2026-10-06

Integrity hash

declared (sri)

package registry · 2026-10-06

Signature / provenance

signed

package registry · 2026-10-06

Dependency advisories

none known

npm audit · 2026-10-08

Popularity

168 downloads a month

package registry · 2026-10-06

Publisher signals

owner: an organization · repository age: 31–90 days · stars: 0–9 · build record: signed

api.github.com · 2026-10-06

Maintenance

active

api.github.com · 2026-10-06

Environment

either (remote or your machine)

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.almostjacked/hevy-mcp: MCP server record.” Data checked 2026-10-08. https://protocolprobe.com/mcp/servers/io.github.almostjacked/hevy-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can authorize a full test.

Write to hello@protocolprobe.com · corrections log · methodology