The MCP server names stdio explicitly and closes cleanly on shutdown; an http mode exists uncalled.
The builder accepts an http kind that disables background tasks and unsandboxed commands, but no caller requests it.
What's wrong with this entry?
The startup path for Claude Code's MCP server now explicitly asks for the stdio transport and registers a hook that closes the server on shutdown. The builder accepts an alternative http kind that disables background tasks and unsandboxed commands before serving; no caller in this build requests it.
createMCPServer
Strings lifted out of the shipped bundle, so the claim above can be checked against them.