{"version":"2.1.246","anchor":"a-check-for-a-disconnected-mcp-client-exists-with-no-caller","canonical_anchor":"a-check-for-a-disconnected-mcp-client-exists-with-no-caller","heading":"A check for a disconnected MCP client exists with no caller","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/a-check-for-a-disconnected-mcp-client-exists-with-no-caller","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### A check for a disconnected MCP client exists with no caller\n\nA check for whether an MCP client has been disconnected exists with no callers.\n\n**What**\n\nA new test sits next to the MCP client shutdown helpers that reports whether a client has no transport attached, meaning it was never connected or has been torn down. The function name appears once in the build, at its own definition.\n\n**Details**\n\n- No caller means nothing currently uses it to decide on a reconnect or a disconnect.\n\n**Evidence**\n\n`\"transport\" in t && t.transport === void 0`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Present in the build but not switched on"}