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.

WHOOP Health Signals

NPM · MCP-SERVER-WHOOP

Local-first, read-only WHOOP MCP server for recovery, sleep, strain, workouts, and body signals

Available components

−2 this week 87 Trust /100

Last scanned (19 hours ago)

Scores higher than 91% 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 @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 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 Yadheedhya06/mcp-server-whoop). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 109 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 407 tokens (~81/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
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 −2
    • Stability: pass → 0.87 functional
  • 29 Oct 26 0
    • CVE-2026-118663 affects this package: high ▼ security
  • 28 Oct 26 0
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
  • 24 Oct 26 0
    • CVE-2023-54404 affects this package: high ▼ security
  • 23 Oct 26 +1
    • Stability: 0.97 → pass security
  • 21 Oct 26 −1
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • Stability: pass → 0.93 functional
  • 17 Oct 26 +3
    • Stability: 0.77 → pass security
  • 16 Oct 26 −3
    • Stability: pass → 0.77 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 4 Nov 2026 · Analysed npm/mcp-server-whoop@0.2.2

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 Yadheedhya06/mcp-server-whoop
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Yadheedhya06/mcp-server-whoop/.github/workflows/publish.yml@refs/tags/v0.2.2
Rekor log index 2189672904
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:b78978bcf3a8697c5b54d13ef5d2f59fd91993b46f378d6da164b17bfbcfeeaa30c2c3ef74464fd5ed70b23aa3610266e80151742bd74fbb234d4fb3a

Background: How many MCP packages publish verified provenance →

Vulnerabilities 8 findings
ID CVE Severity Vector Fix available
GHSA-rmxm-3fg6-px4f CVE-2026-118663 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
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 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~306 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
whoop_cycle_strain_history ~59

Recent local physiological-cycle processing state and finalized metrics for SCORED records; a PENDING_SCORE current cycle may expose only provisional_strain.

NameTypeReqDescription
daysinteger–Number of recent days to fetch, from 1 to 180
NameTypeReqDescription
countnumberyes–
recordsarrayyes–
window_daysnumberyes–

No examples provided.

whoop_latest_overview ~49

Compact local-time coaching overview with newest sleep status, matching current recovery only when ready, finalized strain or explicitly provisional live current-cycle strain, latest workout, recent activity types, and body measurement.

Input schema present but exposes no named parameters.

NameTypeReqDescription
body_measurementobjectyes–
current_cycle–yes–
latest_workout–yes–
recent_activitiesarrayyes–
recovery–yes–
sleep–yes–
statusobjectyes–

No examples provided.

whoop_recovery_history ~65

Recent recovery processing state and, only when WHOOP marks a record SCORED, recovery score, HRV, resting heart rate, SpO2, and skin temperature.

NameTypeReqDescription
daysinteger–Number of recent days to fetch, from 1 to 180
NameTypeReqDescription
countnumberyes–
recordsarrayyes–
window_daysnumberyes–

No examples provided.

whoop_sleep_history ~75

Recent local bedtime/wake time, sleep or nap type, processing state, and finalized sleep metrics only when WHOOP marks a record SCORED.

NameTypeReqDescription
daysinteger–Number of recent days to fetch, from 1 to 180
include_napsboolean–Include naps as well as primary sleep
NameTypeReqDescription
countnumberyes–
recordsarrayyes–
window_daysnumberyes–

No examples provided.

whoop_workout_history ~58

Recent workout sport, local time, duration, and processing state, with score-derived metrics only when WHOOP marks a record SCORED.

NameTypeReqDescription
daysinteger–Number of recent days to fetch, from 1 to 180
NameTypeReqDescription
countnumberyes–
recordsarrayyes–
window_daysnumberyes–

No examples provided.

Install

How do I install the WHOOP Health Signals MCP server?

WHOOP Health Signals runs locally as an npm package, launched with npx -y mcp-server-whoop. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-server-whoop

# add to Claude Code
claude mcp add yadheedhya06-mcp-server-whoop -- npx -y mcp-server-whoop
Common questions

What is the WHOOP Health Signals MCP server?

WHOOP Health Signals is an MCP server listed in the public MCP registry as io.github.Yadheedhya06/mcp-server-whoop. Local-first, read-only WHOOP MCP server for recovery, sleep, strain, workouts, and body signals. This page covers its npm package (mcp-server-whoop).

Is the WHOOP Health Signals MCP server safe to use?

WHOOP Health Signals scores 87 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 4 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 WHOOP Health Signals MCP server expose?

WHOOP Health Signals exposes 5 tools: whoop_latest_overview, whoop_recovery_history, whoop_sleep_history, whoop_cycle_strain_history, whoop_workout_history. Their descriptions and schemas cost roughly 306 tokens of context every time the server is loaded.

Is the WHOOP Health Signals MCP server still maintained?

WHOOP Health Signals is still listed as active in the MCP registry. We last reached this channel on 4 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 WHOOP Health Signals MCP server under?

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