mcp-oauth-setup

No clear malware behavior is present. The OAuth flow includes signed state and PKCE, but discovery and registration permit server-side requests to unvalidated destinations, and unvalidated token endpoints can receive sensitive OAuth credentials. Validate schemes, hosts, resolved IPs, redirects, and endpoint relationships before making requests; treat metadata as untrusted.

No clear malicious behavior is present. The main risks are unvalidated OAuth endpoint destinations that may permit SSRF or credential disclosure, acceptance of HTTP URLs, and unencrypted custom header storage. Endpoint validation, HTTPS enforcement, and careful handling of discovery data are advisable.