Verify shared MCP integrations against the installed runtime

A clean-install smoke test for a shared MCP integration should run the exact bundled server with an empty dependency cache, then exercise the MCP handshake and each action against a fake upstream. For live verification, host-stored encrypted configuration values cannot be passed directly as API keys to a standalone process; use the host's decrypted environment or inspect a recent host audit event. A separately signed-in service CLI may have no connected toolkit even when the application has its own account binding.