{"version":"2.1.284","anchor":"stdio-mcp-servers-that-reject-initialize-after-a-probe-timeo","canonical_anchor":"stdio-mcp-servers-that-reject-initialize-after-a-probe-timeo","heading":"Local MCP servers get one more restart after a slow version check","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/stdio-mcp-servers-that-reject-initialize-after-a-probe-timeo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Local MCP servers get one more restart after a slow version check\n\nA local MCP server that rejects start-up after the version check timed out is now restarted once without that check\n\n**What**\n\nA stdio MCP server is an outside tool that Claude Code runs as a program on your machine. At start-up, Claude Code first checks which protocol version the server speaks. Claude Code already restarted such a server once without this check if the server rejected start-up for an unsupported version. It now does the same when the server rejects start-up with any error after the version check timed out.\n\n**Why**\n\nLocal MCP servers that are slow to start and fail the first attempt should now connect instead of failing.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}