In case anyone still doubts this without even bothering to check, here are some easy keyserver links showing a bunch of signatures on the QMSK:
http://hkps.pool.sks-keyservers.net/pks/lookup?op=vindex&fingerprint=on&search=0xDDFA1A3E36879494
https://keyserver.ubuntu.com/pks/lookup?search=0xddfa1a3e36879494&fingerprint=on&op=index
http://keys.gnupg.net/pks/lookup?op=vindex&fingerprint=on&search=0xDDFA1A3E36879494
Edit: It just occurred to me that perhaps the reason the commenter thinks that the QMSK has no signatures is due to a recent change in GnuPG itself. As you may recall, back in mid-2019 there was a certificate flooding attack. In response, the GnuPG developers released a new version that ignores all key signatures received from keyservers by default. This resulted in unexpected behavior for some users, who helped us to update our verifying signatures documentation to add --keyserver-options no-self-sigs-only,no-import-clean. If the commenter was not using these keyserver options when receiving the QMSK (or any key, for that matter) from a keyserver, it would appear that the QMSK (or any key) has no signatures at all. However, with these keyserver options, gpg receives the QMSK along with 70+ key signatures on it.