WHOOP MCP by usefulapi
io.usefulapi/whoopusefulapi.iostreamable-httpv1.40.4Scanned
Read WHOOP recovery, sleep, cycles, workouts and body measurements.
10 tools: 1 change things and 9 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the WHOOP MCP by usefulapi can do
The WHOOP MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 10 tools. It can create or change data (1 tool: whoop_body_measurement), but cannot delete data. 9 tools only read.
1 tool reads private data (whoop_get_profile); 1 tool brings in text other people can write (whoop_get_profile).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Changes things 1Claude Code: ask
whoop_body_measurementThe user's body measurements (height in meters, weight in kilograms, max heart rate).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The user's body measurements (height in meters, weight in kilograms, max heart rate). WHOOP REST: GET /v2/user/measurement/body. Scope: read:body_measurement.
Annotations the server declares
- title: Get body measurement
- readOnlyHint: true
Only reads 9Show 9 read-only tools
whoop_get_cycleGet a single physiological cycle by its id (strain, kilojoules, average/max heart rate, start/end).No findings
Why it is in this group
- The name "whoop_get_cycle" says "get": a word for reading.
Description, as the server wrote it Get a single physiological cycle by its id (strain, kilojoules, average/max heart rate, start/end). WHOOP REST: GET /v2/cycle/{cycleId}. Scope: read:cycles.
Annotations the server declares
- title: Get cycle
- readOnlyHint: true
whoop_get_cycle_recoveryGet the recovery scored for a specific cycle (recovery %, resting heart rate, HRV RMSSD, SpO2 %, skin temperature).No findings
Why it is in this group
- The name "whoop_get_cycle_recovery" says "get": a word for reading.
Description, as the server wrote it Get the recovery scored for a specific cycle (recovery %, resting heart rate, HRV RMSSD, SpO2 %, skin temperature). WHOOP REST: GET /v2/cycle/{cycleId}/recovery. Scope: read:recovery.
Annotations the server declares
- title: Get cycle recovery
- readOnlyHint: true
whoop_get_profileThe current user's basic WHOOP profile (user id, email, first name, last name).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "whoop_get_profile" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it The current user's basic WHOOP profile (user id, email, first name, last name). WHOOP REST: GET /v2/user/profile/basic. Scope: read:profile.
Annotations the server declares
- title: Get profile
- readOnlyHint: true
whoop_get_sleepGet a single sleep activity by its id (stage summary, sleep needed, respiratory rate, sleep performance %, start/end).No findings
Why it is in this group
- The name "whoop_get_sleep" says "get": a word for reading.
Description, as the server wrote it Get a single sleep activity by its id (stage summary, sleep needed, respiratory rate, sleep performance %, start/end). WHOOP REST: GET /v2/activity/sleep/{sleepId}. Scope: read:sleep.
Annotations the server declares
- title: Get sleep
- readOnlyHint: true
whoop_get_workoutGet a single workout by its id (sport, strain, average/max heart rate, distance, zone durations, start/end).No findings
Why it is in this group
- The name "whoop_get_workout" says "get": a word for reading.
Description, as the server wrote it Get a single workout by its id (sport, strain, average/max heart rate, distance, zone durations, start/end). WHOOP REST: GET /v2/activity/workout/{workoutId}. Scope: read:workout.
Annotations the server declares
- title: Get workout
- readOnlyHint: true
whoop_list_cyclesList the user's physiological cycles (a WHOOP 'day', ~24h anchored to sleep), most recent first.No findings
Why it is in this group
- The name "whoop_list_cycles" says "list": a word for reading.
Description, as the server wrote it List the user's physiological cycles (a WHOOP 'day', ~24h anchored to sleep), most recent first. Each cycle carries a score with day strain, kilojoules burned, and average/max heart rate. Paginated (limit/nextToken) and filterable by created-time window (start/end). WHOOP REST: GET /v2/cycle. Scope: read:cycles.
Annotations the server declares
- title: List cycles
- readOnlyHint: true
whoop_list_recoveriesList the user's recoveries, most recent first.No findings
Why it is in this group
- The name "whoop_list_recoveries" says "list": a word for reading.
Description, as the server wrote it List the user's recoveries, most recent first. Each recovery scores how ready the body is (recovery %, resting heart rate, HRV RMSSD, SpO2 %, skin temperature) and links to its cycle and sleep. Paginated (limit/nextToken) and filterable by created-time window (start/end). WHOOP REST: GET /v2/recovery. Scope: read:recovery.
Annotations the server declares
- title: List recoveries
- readOnlyHint: true
whoop_list_sleepList the user's sleep activities, most recent first.No findings
Why it is in this group
- The name "whoop_list_sleep" says "list": a word for reading.
Description, as the server wrote it List the user's sleep activities, most recent first. Each carries a score with sleep-stage summary, sleep needed, respiratory rate, and sleep performance %. Paginated (limit/nextToken) and filterable by created-time window (start/end). WHOOP REST: GET /v2/activity/sleep. Scope: read:sleep.
Annotations the server declares
- title: List sleep
- readOnlyHint: true
whoop_list_workoutsList the user's workouts, most recent first.No findings
Why it is in this group
- The name "whoop_list_workouts" says "list": a word for reading.
Description, as the server wrote it List the user's workouts, most recent first. Each carries a score with strain, average/max heart rate, distance (meters), and per-heart-rate-zone durations. Paginated (limit/nextToken) and filterable by created-time window (start/end). WHOOP REST: GET /v2/activity/workout. Scope: read:workout.
Annotations the server declares
- title: List workouts
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://whoop.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://whoop.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://whoop.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://whoop.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http whoop https://whoop.usefulapi.io/mcpclaude mcp add --transport http whoop https://whoop.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__whoop__whoop_get_profile",
"mcp__whoop__whoop_list_cycles",
"mcp__whoop__whoop_get_cycle",
"mcp__whoop__whoop_get_cycle_recovery",
"mcp__whoop__whoop_list_recoveries",
"mcp__whoop__whoop_list_sleep",
"mcp__whoop__whoop_get_sleep",
"mcp__whoop__whoop_list_workouts",
"mcp__whoop__whoop_get_workout"
],
"ask": [
"mcp__whoop__whoop_body_measurement"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as whoop. Review it before you use it.
Capability tags behind 1 rule
- mcp__whoop__whoop_get_profile private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/whoop/verify?hash=98026775993d1c62c1e30a7b6381d42d5e1b30c365cd20be663e42f55c786efc" | jq -e '.changed == false'Pinned hash 98026775993d, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/whoop/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/whoop)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
WHOOP MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the WHOOP MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 10 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the WHOOP MCP by usefulapi delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the WHOOP MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the WHOOP MCP by usefulapi have?
- 10 tools: 1 write, 9 read. whoop_body_measurement, whoop_get_profile, whoop_list_cycles, whoop_get_cycle, whoop_get_cycle_recovery, whoop_list_recoveries, whoop_list_sleep, whoop_get_sleep and 2 more.
Does the WHOOP MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the WHOOP MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the WHOOP MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.