{"version":"2.1.242","anchor":"mcp-oauth-stops-sending-a-client-id-that-only-works-for-loop","canonical_anchor":"mcp-oauth-stops-sending-a-client-id-that-only-works-for-loop","heading":"MCP OAuth stops sending a client id that only works for loopback","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/mcp-oauth-stops-sending-a-client-id-that-only-works-for-loop","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### MCP OAuth stops sending a client id that only works for loopback\n\nMCP OAuth stops sending a client id that only works for loopback, and repairs saved entries.\n\n**What**\n\nBoth MCP OAuth providers now withhold the metadata-document URL as the client id whenever the redirect URI is not that document's loopback `\/callback` address, falling back to a configured client or dynamic registration instead. A saved client entry holding a stale metadata URL as its client id is repaired in place.\n\n**Details**\n\n- `MCP_OAUTH_CLIENT_METADATA_URL` still overrides which document URL is used.\n\n**Evidence**\n\n`stale CIMD client_id repair`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}