I'm willing to take a look at it.
What I would do is I'd split this into three pages:
1. The current master server (but without the past games). This can refresh and supports desktop alerts (refresh works to a limited degree without JS). The filter system is already in-place and supported with and without JS. The filter is activated by clicking on a version. I would add a dropdown box or something to make it more obvious.
2. A list of past games (up to a certain date). We should be able to expand these to see the game's stats (as we already can with past games).
3. A proper high scores page, which would allow us to sort players by things like games played, time in game, etc. I think we could probably add other scoring techniques such as units created, killed, etc (since the endgame stats are sent). There isn't really any way of preventing cheating though. If implemented, the high scores should be considered "just for fun". I'm not really sure it's even worth the trouble given that you can create a HTTP request without even playing a game. And I don't see adding security as feasible or a good use of time.
I think the API should be better documented, too. I don't think there's any documentation besides the limited readme and reading the source files directly.
I would put these files on separate pages with the "current games" (#1 above) being the index page and the others being linked from that page.