{"version":"2.1.265","anchor":"mcp-resource-metadata-fetch-de-duplication-discovery-state","canonical_anchor":"mcp-resource-metadata-fetch-de-duplication-discovery-state","heading":"MCP resource metadata fetch de-duplication \/ discovery-state error type changed","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/mcp-resource-metadata-fetch-de-duplication-discovery-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### MCP resource metadata fetch de-duplication \/ discovery-state error type changed\n\nInternal renames in the MCP OAuth login flow's error handling, with no apparent change in behavior\n\n**Unclear.** Whether this is purely a rename or also changes how discovery-state errors are detected in some edge case is not established by the evidence.\n\n**What**\n\nInternal code in the MCP (Model Context Protocol) OAuth login flow was reworked: the check for a discovery-state error now looks for a differently-named error type, and several \"persist failed\" logging calls were renamed to use a different helper. This happened in both the regular and enterprise variants of the MCP OAuth client.\n\n**Why**\n\nThese look like internal renames rather than a behavior change, so there's likely nothing for users to notice here.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}