Unless you are very disciplined, Blazor almost encourages the old Win32/WinForms style of writing code where the business logic gets mixed in with the UI. This is almost equivalent to using MVC, but all the work happens in the View. The funny thing though is that most people's first foray in MVC leads to implementations where almost all the logic is in the Controller including micromanaging all aspects of the View. If you can write code that way, then you can then write Blazor code with almost everything in the Controller.
What you want to really do is have code in the Razor pages be focused on doing View specific stuff; the code in the Model focused in implementing the problem domain; and the Controller simply being a coordinator...