We take security vulnerabilities seriously. If you discover a security vulnerability in MCP-B, please follow these steps:

1. Do not create a public GitHub issue for the vulnerability
2. Email the maintainer directly at bjoern.bethge@gmail.com
3. Include the following information:
   • Description of the vulnerability
   • Steps to reproduce
   • Potential impact
   • Any suggested fixes (optional)

• Initial Response: Within 48 hours
• Assessment: Within 7 days
• Fix Timeline: Depends on severity
  • Critical: Within 24 hours
  • High: Within 7 days
  • Medium: Within 30 days
  • Low: Next scheduled release

When using MCP-B:

1. Keep dependencies up to date
2. Use virtual environments
3. Review code before executing dynamic content
4. Follow the ETHIC principles for AI safety
5. Validate all inputs in agent communication

We appreciate responsible disclosure of security vulnerabilities.