Hi Steven,
Jeroen is correct, but I would like to clarify that the NCBI is not at fault here. They don't change or remove published transcript mappings.
The gist you probably found [1] lists the most recent MapView files available for each assembly. For hg19, that's annotation release 105 (based on GRCh37.p13). This apparently does not contain NM_001104.1, but some older MapView file does.
As Jeroen said, the database on our server is the result of accumulation over time. In addition to importing a new MapView release every now and then, we also sometimes import a transcript from the UCSC Genome Browser database if it is not available in the MapView file. And before using the MapView files, we used to get everything from the UCSC for a few years. Unfortunately, this is a manual process which was not documented or tracked, so there's not really a way to get to the exact same database as ours. I'm planning to tackle (a part of) this by managing these imports with Ansible [2].
So I would say the differences between your installation and ours should mainly be historical. For all latest transcript versions, there shouldn't be a difference. If you would really like to have the exact same database I could provide you with a snapshot as a raw database dump. It might be a good idea to provide such a dump as a service at some point.
cheers,
Martijn
[1]
https://gist.github.com/martijnvermaat/ce84945d05b4e42d3584[2]
https://github.com/mutalyzer/ansible-role-mutalyzer/issues/6