{"version":"2.1.293","anchor":"unanswered-mcp-calls-get-an-explicit-outcome-unknown-message","canonical_anchor":"unanswered-mcp-calls-get-an-explicit-outcome-unknown-message","heading":"Unanswered MCP calls now tell Claude the outcome is unknown","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/unanswered-mcp-calls-get-an-explicit-outcome-unknown-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Unanswered MCP calls now tell Claude the outcome is unknown\n\nWhen a call to an MCP server gets no answer, Claude is told it may have finished, still be running or never started, and to check before repeating\n\n**What**\n\nMCP (the Model Context Protocol) is how Claude Code connects to outside tools and services. Claude Code now has an error code, `mcp_call_unanswered`, for a call to one of those tools that got no answer. The message that goes with it tells Claude that the call:\n\n- may have finished\n\n- may still be running\n\n- may never have started\n\nIt then tells Claude to check what the call did before it repeats it.\n\n**Why**\n\nSome actions should not happen twice, such as sending a message or creating a record. Telling Claude to check first makes it less likely to repeat an action that may already have taken place.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}