This software interacts with real trading accounts and real money. Security is critical.
DO NOT create a public GitHub issue for security vulnerabilities.
Instead, please email: [email protected] (or open a private security advisory)
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Initial response: 48 hours
- Status update: 7 days
- Fix timeline: depends on severity
-
Never commit credentials
- Use
.envfiles (gitignored) - Use environment variables in production
- Use
-
Limit API scopes
- Only enable scopes you need
- Use read-only access when possible
-
Enable
ENABLE_LIVE_TRADING=false- Keep disabled until you're ready
- Test with paper trading first
-
Set
MCP_AUTH_TOKEN- Always use authentication in production
- Use strong, random tokens
-
Network isolation
- Don't expose port 7698 to the internet
- Use reverse proxy with TLS
- Never log sensitive data (full account numbers, tokens)
- Use
crypto.randomUUID()for session IDs - Validate all user inputs
- Follow principle of least privilege
| Version | Supported |
|---|---|
| 1.x | ✅ |
| < 1.0 | ❌ |
We thank security researchers who responsibly disclose vulnerabilities.