console-mcp-server

The server includes an `/mcp-internal` endpoint that explicitly bypasses authentication and proxies headers, intended for 'trusted networks'. While documented as such, this design introduces a critical security risk if misconfigured or exposed to untrusted environments. Authentication for the primary `/mcp` endpoint supports OAuth2.1 and Service Accounts, with dynamic client registration and token management handled internally, which is generally robust. No obvious hardcoded secrets or malicious patterns (like `eval`) were found directly in the provided source.