A standard SSL setup does not provide any security benefit to the server, per se. They do know that the they traffic two and from the endpoint which made the encrypted request has not been manipulated in transit, but there are no guarantees that the endpoint which made the request is not serving as a MITM.

It is possible to configure SSL to configure SSL in such a way where you can validate the clients. Most webservers (Apache, nginx, IIS, etc.) will allow you to set up client certificate-based authentications, meaning each client which is accessing the website will have their own unique certificate, and the webserver will not serve pages to any client which does not have a valid certificate. Distributing and maintaining the client certificates is a large amount of overhead, so this type of setup is usually only done in environments with a limited number of clients, such as intranet apps, APIs with a small number of users, etc.

A standard SSL setup does not provide any security benefit to the server, per se. They do know that the they traffic two and from the endpoint which made the encrypted request has not been manipulated in transit, but there are no guarantees that the endpoint which made the request is not serving as a MITM.

It is possible to configure SSL in such a way where you can validate the clients. Most webservers (Apache, nginx, IIS, etc.) will allow you to set up client certificate-based authentications, meaning each client which is accessing the website will have their own unique certificate, and the webserver will not serve pages to any client which does not have a valid certificate. Distributing and maintaining the client certificates is a large amount of overhead, so this type of setup is usually only done in environments with a limited number of clients, such as intranet apps, APIs with a small number of users, etc.