{"version":"2.1.310","anchor":"mcp-handshake-classifier-now-also-recognises-toolslist","canonical_anchor":"mcp-handshake-classifier-now-also-recognises-toolslist","heading":"MCP tool-list requests are now told apart from setup requests","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/mcp-handshake-classifier-now-also-recognises-toolslist","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### MCP tool-list requests are now told apart from setup requests\n\nClaude Code now classifies requests that list an MCP server's tools separately from the server's opening setup requests\n\n**Unclear.** What the separate handling of tool-list requests changes for users is not known.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. When Claude Code inspects requests sent to one, it used to only mark whether a request was part of the opening setup. It now sorts requests into:\n\n- setup, for the opening handshake messages\n\n- listing, for requests that ask the server for its list of tools\n\n- neither, for everything else\n\n**Why**\n\nThis suggests requests that list a server's tools may now be handled differently from setup traffic, for example with their own timeouts or retries.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}