layered-memory-mcp

The project demonstrates a robust and proactive approach to security. It includes comprehensive input validation using Zod and a custom `RequestValidator` with content sanitization to prevent XSS/injection attacks. Authentication is JWT-based with `bcrypt` for password hashing, and authorization uses RBAC with clear permission structures. Rate limiting is implemented for various operations. Critical environment variables like `AUTH_SECRET`/`JWT_SECRET` are explicitly checked in production, with the system designed to exit if not properly configured, preventing hardcoded production secrets. Default admin/user credentials ('admin123', 'user123') exist for initial setup in development environments but are hashed. Error handling is structured with recovery mechanisms and circuit breakers. External dependencies like Neo4j and FAISS are integrated with appropriate error handling. The extensive compliance documentation (`README`) reflects a strong security-first mindset.