Yes from what I understand......
Oo brought data and code together into an object. In that an object should store data and work on that data. And that you should not have an object that does not do both.
Mvc splits it up again. So
M - model you data, this is not a complete object in that it does not need to do anything but hold data. A typedef so to speak.
V - view the gui for the data. Usually some kind of form again no need for code. It's a but like html and css without the JavaScript.
C - controller the controlling code.
Hence Mvc is not strict oo because oo never really worked anyway. True you can complement it with some oo principles. But there is no reason to not write a Mvc based program with no objects at all. Just data, display and code which Mvc encourages you to keep separate. But the oo design pattern brought it together......
Hmm would make an interesting uni essay :-)
I'll point out we are talking design patterns here NOT languages. They are different.
Peter