{"version":"2.1.227","anchor":"a-failing-mcp-credential-read-no-longer-aborts-the-request","canonical_anchor":"a-failing-mcp-credential-read-no-longer-aborts-the-request","heading":"A failing MCP credential read no longer aborts the request","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/a-failing-mcp-credential-read-no-longer-aborts-the-request","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### A failing MCP credential read no longer aborts the request\n\nAn unreadable MCP credential store no longer kills your request; you get a retryable message.\n\n**What**\n\nToken lookups in the MCP authentication paths now return nothing on failure rather than throwing, and an unreadable credential store gets its own message saying nothing was sent and the request can be retried.\n\n**Details**\n\n- The message reads: Stored credentials for MCP server \"name\" could not be read right now. Nothing was sent. Retry the request.\n- MCP connection-timeout errors are now built by a shared helper instead of inline.\n\n**Evidence**\n\n`Stored credentials for MCP server \"${e}\" could not be read right now. Nothing was sent. Retry the request.`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}