{"version":"2.1.296","anchor":"mcp-initialized-notification-answer-time-recorded","canonical_anchor":"mcp-initialized-notification-answer-time-recorded","heading":"MCP connection diagnostics now record when the server finished its startup handshake","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/mcp-initialized-notification-answer-time-recorded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### MCP connection diagnostics now record when the server finished its startup handshake\n\nMCP connection diagnostics now note the time an MCP server successfully answered the start-up notification\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. When Claude Code connects to one, it sends a notification saying the connection is ready. Claude Code already recorded whether that notification got a successful answer. It now also records the moment the answer arrived, in the diagnostics it keeps about each MCP connection.\n\n**Why**\n\nThis only adds diagnostic detail, which can help when working out why an MCP server is slow to connect. MCP servers behave the same as before.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}