{"version":"2.1.315","anchor":"mcp-url-and-authservermetadataurl-length-limits","canonical_anchor":"mcp-url-and-authservermetadataurl-length-limits","heading":"MCP configs now reject addresses that are too long","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/mcp-url-and-authservermetadataurl-length-limits","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### MCP configs now reject addresses that are too long\n\nAn MCP server's authServerMetadataUrl, and other addresses, now fail validation if they are too long\n\n**What**\n\nIn an MCP server's sign-in settings, `authServerMetadataUrl` used to be checked only for being an https address. It is now also rejected if it is too long. Claude Code also has a new general address check that fails with \"url is too long\".\n\n**Why**\n\nMCP configurations with oversized addresses now fail with an error instead of being accepted.\n\n- Area: MCP\n- Names: `authServerMetadataUrl`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}