Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fitness Tools

NPM · @ALMOSTJACKED/FITNESS-TOOLS-MCP · 2 COMPONENTS

Deterministic fitness calculators — TDEE, adaptive TDEE, body fat, 1RM, macros — with consensus.

−1 this week 82 Trust /100

Last scanned (19 hours ago)

Scores higher than 72% of npm servers

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to almostjacked/fitness-tools). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 103 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability52
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1010 tokens (~101/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 2% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 −1
    • Stability: pass → 0.90 functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −6
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 22 Oct 26 +1
    • Stability: 0.97 → pass security
  • 21 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +3
    • Stability: 0.80 → pass security
  • 16 Oct 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@almostjacked/fitness-tools-mcp@0.3.4

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo almostjacked/fitness-tools
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/almostjacked/fitness-tools/.github/workflows/release.yml@refs/heads/main
Rekor log index 2236077596
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:330bdb8ae3d933b085bdbac90233b2c8dbc25c3fdfdafb06b80fdeefb49b34b5ce70c0c530b0f9b0b225d24e0b3ba2be7ec52cb87d74fa4ce81f11083

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 96 packages
Packages resolved 96
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~1,010 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
activity-multiplier ~95

Estimate the TDEE activity multiplier via the classic lookup table or a NEAT+EAT model (occupation/steps for non-exercise, training volume for exercise).

NameTypeReqDescription
activity_level–––
bmr–––
intensity–––
methods–––
occupation–––
session_minutes–––
sessions_per_week–––
steps_per_day–––
weight–––
NameTypeReqDescription
consensus–yes–
resultsarrayyes–
skippedarrayyes–

No examples provided.

adaptive-tdee ~220

Measure actual TDEE from a logged history of daily weight and/or calorie intake. Default method (kalman) is a joint Kalman filter over true weight and TDEE — handles missing days, gates outliers, and reports uncertainty (CI95) alongside denoised true weight; regression/endpoints are simple window-based estimates kept for comparison. Use instead of formula TDEE once real logged data exists. Each entry needs at least one of weight/kcal (not necessarily both). Entry dates must span 10 years or less (earliest to latest). Note: all methods need at least one weigh-in (kalman) or two (regression/endpoints) — a history with zero weight entries throws under the kalman default; pass methods:'all' to get a graceful empty/skipped result instead.

NameTypeReqDescription
entriesarrayyes–
methods–––
prior_tdee_kcalnumber–Optional starting TDEE estimate, e.g. from the tdee tool; speeds early convergence.
window_daysinteger––
NameTypeReqDescription
consensus–yes–
resultsarrayyes–
skippedarrayyes–

No examples provided.

body-fat ~86

Estimate body-fat % via US Navy circumference, Jackson-Pollock 3-site skinfold, and Deurenberg (BMI-based) methods.

NameTypeReqDescription
age–––
height–––
hip–––
methods–––
neck–––
sexstringyes–
skinfold_sum–––
waist–––
weight–––
NameTypeReqDescription
consensus–yes–
resultsarrayyes–
skippedarrayyes–

No examples provided.

ffmi ~77

Compute the Fat-Free Mass Index (FFMI) and its height-adjusted form from weight and body fat (or lean mass), and flag whether it exceeds the ~25 natural ceiling.

NameTypeReqDescription
body_fat–––
heightobjectyes–
lean_mass–––
methods–––
weightobjectyes–
NameTypeReqDescription
consensus–yes–
resultsarrayyes–

No examples provided.

macros ~78

Compute protein/fat/carb grams for a calorie target using the g-per-kg-bodyweight method, with goal-based protein defaults.

NameTypeReqDescription
caloriesnumberyes–
fat_g_per_kg–––
goalstring––
methods–––
protein_g_per_kg–––
weightobjectyes–
NameTypeReqDescription
consensus–yes–
resultsarrayyes–

No examples provided.

muscle-potential ~95

Estimate drug-free maximum bodyweight at a target body-fat % via Casey Butt (wrist+ankle), the FFMI~25 natural cap, and Berkhan's max-contest-weight model. Men only in v1.

NameTypeReqDescription
ankle–––
heightobjectyes–
methods–––
sexstringyes–
target_body_fat_pctnumber––
wrist–––
NameTypeReqDescription
consensus–yes–
resultsarrayyes–
skippedarrayyes–

No examples provided.

one-rep-max ~71

Estimate 1RM from a submaximal set via Epley, Brzycki, Lombardi, Wathan, O'Conner, and Mayhew; returns a %1RM load chart.

NameTypeReqDescription
methods–––
repsintegeryes–
weightobjectyes–
NameTypeReqDescription
consensus–yes–
percent_tablearrayyes–
resultsarrayyes–

No examples provided.

powerlifting-attempts ~77

Deterministic opener/second/third attempts from an estimated 1RM, plus a warmup ramp and per-side plate loading. Tunable by aggressiveness and available plates.

NameTypeReqDescription
aggressivenessstring––
available_plates–––
bar_weight–––
one_rep_maxobjectyes–
NameTypeReqDescription
aggressivenessstringyes–
attemptsobjectyes–
bar_weightnumberyes–
unitstringyes–
warmupsarrayyes–

No examples provided.

rsmi ~106

Estimate the appendicular skeletal muscle index (RSMI) from a DXA value (direct) and/or an anthropometric estimate (Wen 2011), and flag low muscle mass against EWGSOP2, AWGS, and Baumgartner sarcopenia cutoffs.

NameTypeReqDescription
agenumberyes–
asm_kg–––
heightobjectyes–
methods–––
sexstringyes–
weightobjectyes–
NameTypeReqDescription
consensus–yes–
resultsarrayyes–
skippedarrayyes–

No examples provided.

tdee ~105

Estimate BMR and TDEE via Mifflin-St Jeor, Harris-Benedict, Katch-McArdle, and Cunningham. Provide body_fat or lean_mass to unlock the LBM-based methods.

NameTypeReqDescription
activity–yes–
agenumberyes–
body_fat–––
heightobjectyes–
lean_mass–––
methods–––
sexstringyes–
weightobjectyes–
NameTypeReqDescription
consensus–yes–
resultsarrayyes–
skippedarrayyes–

No examples provided.

Install

How do I install the Fitness Tools MCP server?

Fitness Tools runs locally as an npm package, launched with npx -y @almostjacked/fitness-tools-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @almostjacked/fitness-tools-mcp

# add to Claude Code
claude mcp add almostjacked-fitness-tools -- npx -y @almostjacked/fitness-tools-mcp
Common questions

What is the Fitness Tools MCP server?

Fitness Tools is an MCP server listed in the public MCP registry as io.github.almostjacked/fitness-tools. Deterministic fitness calculators, TDEE, adaptive TDEE, body fat, 1RM, macros, with consensus. This page covers its npm package (@almostjacked/fitness-tools-mcp).

Is the Fitness Tools MCP server safe to use?

Fitness Tools scores 82 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Fitness Tools MCP server expose?

Fitness Tools exposes 10 tools: tdee, adaptive-tdee, body-fat, one-rep-max, macros, and 5 more. Their descriptions and schemas cost roughly 1,010 tokens of context every time the server is loaded.

Is the Fitness Tools MCP server still maintained?

Fitness Tools is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Fitness Tools MCP server under?

Fitness Tools declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Fitness Tools MCP server?

VerifyMCP ran 16 checks on Fitness Tools, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.