{"version":"2.1.224","anchor":"two-more-mcp-connections-skip-issuer-metadata-validation","canonical_anchor":"two-more-mcp-connections-skip-issuer-metadata-validation","heading":"Two more MCP connections skip issuer metadata validation","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/two-more-mcp-connections-skip-issuer-metadata-validation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Two more MCP connections skip issuer metadata validation\n\nTwo more MCP transports now skip issuer metadata validation, matching the rest.\n\n**What**\n\nTwo MCP client setup paths now set the same issuer-metadata-validation skip that the other paths already used, so OAuth-backed MCP servers behave consistently across transports.\n\n**Evidence**\n\n`skipIssuerMetadataValidation`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}