whoop-mcp-server (benhursenabathi/whoop-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 32 out of 100, grade F. It declares 7 tools. No publisher has claimed this listing.

F
Warning
32/100

whoop-mcp-server

MCP server that enables AI assistants to access Whoop health data including recovery, sleep, workouts, and daily strain for personalized health recommendations.

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

benhursenabathi

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: WHOOP_CLIENT_SECRET, WHOOP_ACCESS_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tool annotations don’t match behaviour
7 read-only tools perform write/delete/exec — whoop_get_profile (line 55: fs.writeFileSync(TOKEN_FILE_PATH, JSON.stringify(tokens, null, 2), { mode: 0o600 })); whoop_get_body_measurements (line 55: fs.writeFileSync(TOKEN_FILE_PATH, JSON.stringify(tokens, null, 2), { mode: 0o600 })); whoop_get_recovery (line 55: fs.writeFileSync(TOKEN_FILE_PATH, JSON.stringify(tokens, null, 2), { mode: 0o600 }))
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — whoop_get_health_overview (line 55: fs.writeFileSync(TOKEN_FILE_PATH, JSON.stringify(tokens, null, 2), { mode: 0o600 }))
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 3 credentials: WHOOP_ACCESS_TOKEN, WHOOP_CLIENT_SECRET, WHOOP_REFRESH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.24.3GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.24.3GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretWHOOP_ACCESS_TOKENAfter initial setup, you can remove and WHOOP_REFRESH_TOKEN from your config. The server only needs:
configWHOOP_CLIENT_ID## "Missing or WHOOP_CLIENT_SECRET" error
🔐 secretWHOOP_CLIENT_SECRET## "Missing WHOOP_CLIENT_ID or " error
🔐 secretWHOOP_REFRESH_TOKENAfter initial setup, you can remove WHOOP_ACCESS_TOKEN and from your config. The server only needs:
configWHOOP_TOKEN_PATHSet environment variable to store tokens in a specific location:
// quality suggestions

Tool annotations match behaviour

7 read-only tools perform write/delete/exec — whoop_get_profile (line 55: fs.writeFileSync(TOKEN_FILE_PATH, JSON.stringify(tokens, null, 2), { mode: 0o600 })); whoop_get_body_measurements (line 55: fs.writeFileSync(TOKEN_FILE_PATH, JSON.stringify(tokens, null, 2), { mode: 0o600 })); whoop_get_recovery (line 55: fs.writeFileSync(TOKEN_FILE_PATH, JSON.stringify(tokens, null, 2), { mode: 0o600 }))

Either remove the readOnlyHint:true annotation, or remove the write/delete call from the tool handler.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — whoop_get_health_overview (line 55: fs.writeFileSync(TOKEN_FILE_PATH, JSON.stringify(tokens, null, 2), { mode: 0o600 }))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not logged

4 secret values sent to error/log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 2 high severity in production deps — @modelcontextprotocol/sdk@1.24.3 (high), @modelcontextprotocol/sdk@1.24.3 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Tool description accuracy

whoop_get_health_overview: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/benhursenabathi/whoop-mcp-server?variant=verified)](https://m8ven.ai/mcp/benhursenabathi/whoop-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: f9beb5e9b8cd80f2dbcce96a38c4e8ffc7611811
code hash: 5eb7b42d6d91f8d381e837929c3ecfd90055abedf7744a86fc1f9d26e40fd6d3
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client