esus-pec-mcp

The server demonstrates strong security practices: all database queries are read-only and use parameterized inputs to prevent SQL injection. It enforces strict limits on returned data rows (typically 50-200, up to 1000 for SOAP notes) and anonymizes sensitive patient identifiers (e.g., full names are converted to initials). Tools require specific filters to prevent broad data sweeps. Hardcoded database credentials are explicitly stated as defaults for development and users are instructed to override them with environment variables or a .env file for production. No 'eval' or other dynamic code execution patterns were found. The most sensitive data (SOAP notes) requires a specific patient ID and is subject to limits.