{"version":"2.1.293","anchor":"http-mcp-tool-call-watchdog-is-told-when-a-request-fails-wit","canonical_anchor":"http-mcp-tool-call-watchdog-is-told-when-a-request-fails-wit","heading":"Failed tool calls to HTTP MCP servers are no longer treated as still waiting","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/http-mcp-tool-call-watchdog-is-told-when-a-request-fails-wit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Failed tool calls to HTTP MCP servers are no longer treated as still waiting\n\nWhen a tool call to an HTTP MCP server fails with certain errors, Claude Code now marks it as answered instead of still waiting\n\n**Unclear.** Which errors, apart from an expired session, count as an answer is not known.\n\n**What**\n\nMCP servers are add-on services that give Claude extra tools. Claude Code watches each tool call to such a server so it can tell when one is taking too long. For servers reached over HTTP, if sending the call fails with an expired session or with certain other errors, Claude Code now marks the call as answered before passing the error on. Before, a failed send left the call marked as still waiting.\n\n**Why**\n\nThis should stop a call that already failed from later being reported as stuck or timed out.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}