teradata-qg-mcp-server

The server handles sensitive credentials (QueryGrid Manager username/password) by loading them exclusively from environment variables or a .env file, not hardcoding. It uses `requests.Session` for API calls with basic authentication. The ability to disable SSL verification (`QG_MANAGER_VERIFY_SSL=false`) is clearly documented as a 'CRITICAL GOTCHA' for LLMs, with specific tools (like `support_archive_tools`) explicitly instructing AI agents to prompt the user for credentials for file downloads, preventing leakage of pre-configured credentials for potentially sensitive operations. Password requirements for new users are enforced (min. 14 chars, symbols, numbers). Process management commands (`pgrep`, `taskkill`) used for server control appear to be securely handled without direct external input. No `eval` or `exec` statements were found in the provided code snippets. Overall, explicit security considerations are well-integrated.