yandex-tracker-mcp

The server implements multiple robust authentication mechanisms including static OAuth, IAM tokens, and dynamic IAM via service accounts, as well as a full OAuth 2.0 provider with refresh token support. When using Redis for OAuth data or caching, it supports Fernet encryption for tokens at rest and SHA-256 hashing for Redis keys. Secrets are expected to be provided via environment variables, not hardcoded. The OAuth mode requires the server to be publicly accessible for callback URLs, which is a common pattern for OAuth but requires careful network configuration. There are no obvious 'eval', obfuscation, or malicious patterns.