Only the latest release of whop-mcp receives security updates.
| Version | Supported |
|---|---|
| Latest | ✅ Yes |
| Older | ❌ No |
We take security seriously. If you discover a vulnerability in this project, please do NOT open a public GitHub issue.
Instead, report it privately:
📧 Email: furkankoykiran@gmail.com
Subject: [SECURITY] whop-mcp vulnerability report
Please include:
- A description of the vulnerability
- Steps to reproduce
- Potential impact
- Any suggested mitigations (optional)
| Step | Timeframe |
|---|---|
| Acknowledgement | Within 48 hours |
| Initial assessment | Within 5 business days |
| Fix & release | Depends on severity |
- Never hard-code your
WHOP_API_KEYin source code. - Always pass the API key via environment variables.
- Use the minimum permissions required when creating Company API Keys on Whop's Developer Dashboard.
- Rotate your API key immediately if you suspect it has been compromised.
- Do not commit
.envfiles to version control.
This security policy covers vulnerabilities in the whop-mcp MCP server code itself. Issues with the Whop.com API or platform should be reported directly to Whop.com.
⚠️ This is a community-led project and is NOT an official Whop.com product.