Adamic Security Policy Guidelines

Responsible Disclosure

Adamic is committed to ensuring the security of our MCP servers, documentation platform, and related services. We appreciate the security research community's efforts to help us maintain a secure environment.

Our security policy follows industry best practices for responsible disclosure. We believe that working together with security researchers creates a safer environment for everyone who uses our services.

Scope

In Scope

• adamic.tech - Main documentation website
• SQLite MCP Server - Docker images and source code
• Memory Journal MCP Server - Docker images and source code
• Related GitHub repositories under neverinfamous organization
• Docker Hub images under writenotenow namespace

Out of Scope

• Third-party services (Cloudflare, GitHub, Docker Hub infrastructure)
• Social engineering attacks
• Physical security issues
• Denial of service attacks

Reporting Guidelines

When reporting a security vulnerability, please include:

Clear and detailed reports help us understand and address security issues more effectively. The more information you provide, the faster we can work on a resolution.

• Description: Clear description of the vulnerability
• Steps to Reproduce: Detailed steps to reproduce the issue
• Impact: Potential impact and severity assessment
• Proof of Concept: If applicable, include PoC code or screenshots
• Affected Components: Which services or repositories are affected

Our Commitment

• Acknowledgment: We will acknowledge receipt of your report within 48 hours
• Communication: We will keep you informed of our progress
• Credit: We will credit researchers who report valid vulnerabilities (unless you prefer to remain anonymous)
• No Legal Action: We will not pursue legal action against researchers who follow this policy

Security Best Practices

Our services implement several security measures:

Security is built into every aspect of our infrastructure and development process. We continuously monitor and improve our security posture to protect user data and maintain service integrity.

• Static Architecture: Serverless deployment reduces attack surface
• Content Security: Comprehensive security headers via Cloudflare
• Container Security: Non-root Docker containers with minimal privileges
• Input Validation: Parameterized queries and input sanitization in MCP servers
• Regular Updates: Dependencies and base images are regularly updated

Contact Information

For non-security related issues, please use our GitHub repositories for support.

We encourage open communication and transparency in our security practices. Thank you for helping us maintain a secure environment for all users of our MCP servers and documentation platform.