Please do not report security vulnerabilities through public GitHub issues.
If you discover a security vulnerability in this project, please report it privately to help us address it responsibly.
- Email: ashrivastava@ibm.com
- Subject: [SECURITY] Verify MCP Server - Brief Description
- Include:
- Type of vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if available)
- Acknowledgment: Within 48 hours
- Initial Assessment: Within 5 business days
- Resolution: Varies by severity (critical issues prioritized)
When deploying this project:
-
Credentials Management
- Never commit API tokens, passwords, or secrets to version control
- Use environment variables (
.envfiles) for all sensitive configuration - Rotate credentials regularly
-
Network Security
- Use HTTPS for all API communication
- Deploy behind a firewall or VPN for internal use
- Restrict network access to Verify endpoints
-
Access Control
- Use unique API keys per user/client
- Revoke keys immediately when no longer needed
- Follow least privilege principle
-
Monitoring
- Monitor for unusual API usage patterns
- Review server logs regularly
- Set up alerts for authentication failures
| Version | Supported |
|---|---|
| Latest | ✅ |
We follow responsible disclosure. Security issues will be addressed promptly and disclosed after a fix is available.