{"version":"2.1.257","anchor":"mcp-oauth-now-distinguishes-project-level-approval-denial","canonical_anchor":"mcp-oauth-now-distinguishes-project-level-approval-denial","heading":"MCP OAuth now distinguishes project-level approval denial","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/mcp-oauth-now-distinguishes-project-level-approval-denial","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### MCP OAuth now distinguishes project-level approval denial\n\nMCP auth over the remote bridge now reports missing project approval separately from a managed-policy block.\n\nMCP server authentication over the remote bridge now returns a distinct refusal reason when a server lacks project-level approval, separate from the existing managed-policy block message.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}