The aim of an MVP is to test your solution on the market, while minimizing your time and budget.
Indeed, if you're in the product design phase, you can only make assumptions about how your product will be received and used by your target audience.
At this stage, it's therefore important to test the product, equipping it only with its essential functionalities.
The opposite of the MVP is the delivery of a finished product, which has required significant investment both in terms of time and money, and for which we don't know if it exactly meets users' needs. The risk of such an approach is to realize far too late that you've made a mistake, that you've made the wrong assumptions, that 80% of the functionalities you've developed are superfluous, and that you have to start from scratch with a large part of the product.
The MVP enables you to test your hypotheses at an early stage, and to meet your users' expectations as closely as possible.