A check for whether an MCP client has been disconnected exists with no callers.
A disconnected-client test sits beside MCP shutdown helpers, referenced only at its own definition.
What's wrong with this entry?
A 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.
- No caller means nothing currently uses it to decide on a reconnect or a disconnect.
"transport" in t && t.transport === void 0
Strings lifted out of the shipped bundle, so the claim above can be checked against them.