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 · SCANNED SEP 20

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

Available components

npm · mcp-server-whoop 92
0 this week 92 Trust /100
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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 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 Yadheedhya06/mcp-server-whoop). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 64 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 Management90
  • Stability observed for 27 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
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
// .cursor/mcp.json
{
  "mcpServers": {
    "yadheedhya06-mcp-server-whoop": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-whoop"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "yadheedhya06-mcp-server-whoop": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-whoop"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add yadheedhya06-mcp-server-whoop -- npx -y mcp-server-whoop
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yadheedhya06-mcp-server-whoop": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-server-whoop"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add yadheedhya06-mcp-server-whoop --command npx --arg -y --arg mcp-server-whoop
# ~/.hermes/config.yaml
mcp_servers:
  yadheedhya06-mcp-server-whoop:
    command: "npx"
    args: ["-y", "mcp-server-whoop"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "yadheedhya06-mcp-server-whoop": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-server-whoop"
      ]
    }
  }
}
# add to Vellum
assistant mcp add yadheedhya06-mcp-server-whoop -t stdio -c npx -a -y mcp-server-whoop
// mcp.json
{
  "mcpServers": {
    "yadheedhya06-mcp-server-whoop": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-whoop"
      ]
    }
  }
}
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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

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 20 Sept 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 https://slsa.dev/provenance/v1
Subject digest sha512:b78978bcf3a8697c5b54d13ef5d2f59fd91993b46f378d6da164b17bfbcfeeaa30c2c3ef74464fd5ed70b23aa3610266e80151742bd74fbb234d4fb3a

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
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.

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 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.