whoop-postgres-mcp

MCPcommunity
v0.1.0io.github.cunicopia-devUnknownUpdated 10d agoGitHub

Sync WHOOP recovery, sleep, strain, and workouts into Postgres and query them from any MCP client.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
10d agoLast update
Needs 3 credentials before it runs
  • WHOOP_CLIENT_IDOAuth apprequired

    Client ID of your WHOOP developer app (developer.whoop.com).

  • WHOOP_CLIENT_SECRETOAuth apprequired

    Client secret of your WHOOP developer app.

  • WHOOP_DB_URLAPI keyrequired

    Postgres DSN the server syncs into and reads from (e.g. postgresql://user:pass@localhost:5432/whoop). Tokens are stored in this database.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.cunicopia-dev
LicenseUnknown
Version0.1.0
Sourcemcp-registry
GitHubcunicopia-dev/whoop-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
F
10/100Untrusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
—Prompt-injection scan · not run+0/30
→ Not yet scanned — the repository archive is scanned on the next cron run
—Obfuscation / exfil scan · not run+0/20
→ Not yet scanned — the repository archive is scanned on the next cron run
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanNot runHow well does this scan work?
EvalsNone
IndexedSep 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Not scanned yet

Forge has no scan on record for this entry, so it holds no observation of its tool surface. That is an absence of evidence, not evidence that it exposes no tools.

About

Sync WHOOP recovery, sleep, strain, and workouts into Postgres and query them from any MCP client.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.