{"version":"2.1.224","anchor":"mcp-oauth-discovery-cache-is-re-validated-against-policy","canonical_anchor":"mcp-oauth-discovery-cache-is-re-validated-against-policy","heading":"MCP OAuth discovery cache is re-validated against policy","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/mcp-oauth-discovery-cache-is-re-validated-against-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### MCP OAuth discovery cache is re-validated against policy\n\nCached MCP OAuth details are rechecked against policy, so moved servers no longer authenticate stale.\n\n**What**\n\nCached OAuth discovery details for MCP servers are now re-checked against policy before reuse and kept only for a fixed window. If the cached authorization server fails the check, stored credentials are invalidated and the cached entry is cleared instead of being reused, so a server that has moved or been disallowed no longer silently authenticates against a stale endpoint.\n\n**Evidence**\n\n`Returning cached discovery state (authServer: `\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}