We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
Examples of behavior that contributes to a positive environment for our community include:
- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
- Focusing on what is best not just for us as individuals, but for the overall community
- Showing patience with newcomers and those learning
- Providing helpful guidance when reviewing code or discussing technical topics
- Celebrating others' contributions and achievements
- Using welcoming and inclusive language
- Being professional in all interactions
Examples of unacceptable behavior include:
- The use of sexualized language or imagery, and sexual attention or advances of any kind
- Trolling, insulting or derogatory comments, and personal or political attacks
- Public or private harassment of any form
- Publishing others' private information, such as a physical or email address, without their explicit permission
- Doxxing or sharing personal information without consent
- Spamming issues, pull requests, or discussions
- Off-topic discussions that derail productive conversations
- Deliberately intimidating, stalking, or following someone
- Advocating for, or encouraging, any of the above behavior
- Other conduct which could reasonably be considered inappropriate in a professional setting
Given the cybersecurity and blockchain nature of this project:
- Do not share or request real private keys, mnemonics, or sensitive credentials
- Use appropriate test networks and sandbox environments for development
- Report security vulnerabilities responsibly through proper channels (see SECURITY.md)
- Do not perform unauthorized scanning or testing against systems you don't own
- Respect responsible disclosure practices for security research
- Follow ethical hacking guidelines when contributing to security tools
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
This Code of Conduct applies to all project spaces including:
- GitHub repository (issues, pull requests, discussions, code)
- Documentation and wikis
- Community forums and chat channels
- Email communications related to the project
- Social media when representing the project
- Events and conferences where the project is represented
- Third-party platforms where project discussions occur
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
Community Impact: A violation through a single incident or series of actions.
Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
Consequence: A permanent ban from any sort of public interaction within the community.
If you experience or witness unacceptable behavior—or have any other concerns—please report it by contacting the project team at:
- Primary Contact: mr.mazharsaeed790@gmail.com
- Subject Line: "Code of Conduct Violation - [Brief Description]"
- GitHub: Create a private issue or use GitHub's reporting features
When reporting, please include:
- Description of the incident
- Date and time of occurrence
- Location (GitHub issue, PR, discussion, etc.)
- People involved (usernames/handles)
- Screenshots or links if applicable
- Impact on you or the community
- Previous incidents if this is a pattern
All reports will be handled with discretion and confidentiality. We understand that reporting violations can be difficult and we are committed to protecting reporters from retaliation.
- Acknowledgment: We will acknowledge receipt within 24 hours
- Investigation: Thorough review of the incident and evidence
- Decision: Determination of appropriate response based on guidelines
- Communication: Clear communication of decision to all parties
- Follow-up: Monitoring to ensure compliance and prevent retaliation
If you disagree with a moderation decision:
- Email Appeal: Send appeal to mr.mazharsaeed790@gmail.com
- Include Details: Explain why you believe the decision was incorrect
- Review Period: Appeals will be reviewed within 7 days
- Final Decision: The appeal decision is final
- Muhammad Mazhar Saeed (Professor) - Project Founder & Lead Maintainer
- Email: mr.mazharsaeed790@gmail.com
- GitHub: @0x-Professor
- Responsibilities: Overall project direction, final decisions on enforcement
Community leaders are responsible for:
- Setting a positive example through their own behavior
- Responding promptly to Code of Conduct violations
- Making fair and consistent enforcement decisions
- Protecting the community from harmful behavior
- Supporting contributors and maintaining an inclusive environment
- Transparency in moderation decisions when appropriate
We believe in recognizing positive contributions to our community:
Contributors who consistently demonstrate excellent community citizenship may be recognized as Community Champions, receiving:
- Special badge in project documentation
- Highlighted contributions in release notes
- Invitation to join community leadership discussions
- Mentorship opportunities with project maintainers
We regularly celebrate community contributions through:
- Monthly shoutouts in project updates
- Contributor spotlights on social media
- "Thank you" notes in release announcements
- Community awards for exceptional contributions
We encourage continuous learning and growth:
- Mentorship Program: Pairing experienced contributors with newcomers
- Technical Workshops: Regular sessions on MCP development, blockchain, and security
- Code Review Training: Learning effective and constructive code review practices
- Inclusive Communication: Workshops on respectful technical discussions
- Accessibility Guidelines: Making our project accessible to all contributors
- Language Support: Helping non-native English speakers participate effectively
- Time Zone Considerations: Scheduling meetings and events across global time zones
- Cultural Sensitivity: Understanding and respecting cultural differences
This Code of Conduct may be updated periodically to address new situations or improve clarity. Changes will be:
- Discussed openly with the community
- Posted for feedback with a reasonable comment period
- Documented clearly with version history
- Communicated effectively to all community members
- v1.0 (January 2025): Initial Code of Conduct based on Contributor Covenant v2.1
- v1.1 (January 2025): Added security-specific standards and blockchain considerations
This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.
For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
We are committed to making MCP Servers a welcoming and inclusive project for all contributors. Together, we can build the future of decentralized applications with AI-powered automation and enterprise-grade security while maintaining the highest standards of professional conduct and community collaboration.
Questions about this Code of Conduct? Contact us at mr.mazharsaeed790@gmail.com
Made with ❤️ by the MCP Servers community