Skills/PyPI/whoop-mcp

whoop-mcp@0.8.5

VERIFIED· not started

Publisher claims: "Read-only WHOOP v2 API access for MCP clients — direct OAuth, local SQLite cache, CSV/JSONL/Parquet exports" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher ashwanthramkl · publishing for 210 daysInstalls 415Last detonated 16 min ago
$claude mcp add whoop-mcp -- uvx whoop-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
WHOOP_CLIENT_SECRETConfiguration, not credentials: LOG_FILE, WHOOP_CLIENT_ID, WHOOP_DB_PATH, WHOOP_LOG_FILE, WHOOP_LOG_LEVEL, WHOOP_REDIRECT_URI, WHOOP_UPDATE_CHECK
Where it talks to
whoop.com (its own)Also githubusercontent.com — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names githubusercontent.com as well as its own vendor. The guard injects WHOOP_CLIENT_SECRET only into requests to whoop.com (and its subdomains) and refuses the rest.

$vet-skills run --secrets WHOOP_CLIENT_SECRET=whoop.com -- uvx whoop-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-21 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
File permission modification commandsrc/whoop_store.py:19 · File permission modification command — agent changes file ownership/permissions``tokens.json``. The file is created with ``chmod 600`` on firstFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
File permission modification commandsrc/whoop_mcp_server.py:27 · File permission modification command — agent changes file ownership/permissionssensitive as ``tokens.json``. The file is created with ``chmod 600``.Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
File permission modification commandsrc/whoop_store.py:123 · File permission modification command — agent changes file ownership/permissions# Ensure chmod 600 even on an existing file we didn't just create.Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

Cost to the agent

Instructions loaded
≈62 tok
1 file · 42 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.

whoop-mcp@0.8.5 safety verdict: Verified (not started) — KillerSkills