{"version":"2.1.319","anchor":"mcp-proxy-size-limit-error-strings-and-refused-sign-in-token","canonical_anchor":"mcp-proxy-size-limit-error-strings-and-refused-sign-in-token","heading":"Refused MCP sign-in tokens can be tried again after a while","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/mcp-proxy-size-limit-error-strings-and-refused-sign-in-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Refused MCP sign-in tokens can be tried again after a while\n\nClaude Code now recognises two proxy size-limit errors for MCP responses, and a refused sign-in token is retried after a wait\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Two changes affect them:\n\n- Claude Code now recognises two size-limit errors from the Anthropic proxy: one for a whole MCP server response that is too large, and one for a single streamed event that is too long.\n\n- A sign-in token that was refused is no longer refused for good. Claude Code records when the refusal happened, and after a period it may use that token again.\n\n**Why**\n\nOversized MCP responses can be identified, and a token refused once is not locked out for the rest of the session.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}