Out of curiosity I wonder why in the Handshake Protocol of TLS there is an explicit message, i.e. CertificateVerify, that serves to verify that the client is indeed the owner of the certificate he claims to own, while such a message is lacking for the server's certificate? Verification is achieved through signing a hash of the formerly exchanged messages.
In my understanding it is at least equally as important for the server to verify his ownership, because in practice it is often the client who is going to trust the server with delicate information.