Actually the reason for the auto-added server on new network is to prevent a chicken-and-egg problem: after you install just one node, how do you know it's workng? If you install two nodes and they can't talk to each other, how do you know which one (or both) is broken?
hello.ipn.dev helps with those questions, even if it's just a pingable server. But ping is hard to do on iOS or Android, and even on other OSes it requires people to drop to the command line, which can be tough, so we added an https server you can visit from a browser. And then we had to make the https server respond with something, so we added a (go-based) irc server kind of as a joke. (You can also connect using a regular irc client, which is another important test: most BeyondCorp-style products cannot proxy non-http traffic like irc.) More on testing with hello.ipn.dev here: https://tailscale.com/kb/1030/next-steps
The irc server seems to have gotten misconstrued as a tech support mechanism lately, which isn't ideal (since we're a small team and can't monitor it full time), so we'll probably aim to shut it down and redirect people to freenode. But on the other hand, some users like it so we're hesitant to shut it down.
Anyway, other commenters are correct that it's ACLed to not allow outgoing connections; it makes a good demo of a "one way" node. Nevertheless, users who are concerned about keeping their network private should remove the test node from their network, as described here: https://tailscale.com/kb/1073/hello-ipn-dev
-- Avery@Tailscale