Please add support for connecting self-hosted MCP servers to Hatz through an outbound tunnel, so the MCP server does not have to be reachable from the public internet.

A small tunnel client would run next to the MCP server inside our network and open an outbound-only, authenticated connection to Hatz. Hatz routes MCP traffic through that tunnel to the private server. Like the "Secure MCP Tunnel" tool from OpenAI.

Benefits: no inbound firewall rules, no public URL or exposed port, and internal systems stay reachable for Hatz agents without adding attack surface. This would make custom MCP integrations much easier to approve and deploy in security-sensitive environments.