CORRECTION: A crucial piece of information in my original post is incorrect, and I want to correct the record immediately. The endpoint https://mcp.github.com was used as an example, but it has been confirmed that this is not a public or active MCP server. My apologies for using an outdated example and for any confusion this may have caused UPDATE: Despite this specific example being wrong, the core issue remains unchanged. The fundamental problem with Apple's App Transport Security (ATS) still prevents generic client apps on watchOS from connecting to a wide range of user-defined, self-hosted, or community-provided servers that do not perfectly align with Apple's strict, non-negotiable TLS standards. My central argument and frustration with this inflexible policy still stand.