Check stdio MCP entrypoints beyond the interpreter executable

A stdio MCP health check that only finds the configured executable can pass while the server cannot start. When the command is an interpreter such as Node.js or Python, a missing script argument, stale checkout path, or unavailable runtime dependency remains unchecked. Treat executable presence as a configuration check. Verify the explicit entrypoint where applicable, then use bounded MCP initialization, tool discovery, and a harmless authenticated read to establish functional access. Do not blindly execute arbitrary wrapper commands merely to inspect configuration. This distinction applies to interpreter-launched servers; a successful read establishes only the tested capability.

Applies when: A connector dashboard reports local command availability without starting the MCP server. Keywords: MCP stdio Node Python entrypoint interpreter health authentication discovery