Yes and no and it depends. MVC is one of the terms which once had a very specific meaning, but then have grown in use to become a much broader and less specific term.
The original use of MVC was specifically as a oo design pattern used when coding desktop GUIs in Smalltalk. The pattern was specifically concerned about separating the data displayed in a form from the UI controls used to display the data, and the input gestures (mouse clicks etc.) used by the user. This was an early attempt to structure GUI code, and many more refined GUI patterns have developed since (patterns like Model-View-Presenter, Model-View-Viewmodel and so on). Martin Fowler have written a nice overview of the history of the MVC pattern as used in GUIs.
Later someone decided to reuse the term MVC for structuring web applications a certain way. It is not really the same pattern, but you can say that web MVC was inspired by the separation of concerns in the original MVC. It is more of an architecture than a classic pattern though. You will get really confused if you try to apply your understanding of the original MVC pattern to how the terms are used in MCV web apps - for example what is called the view in web-MVC corresponds more or less to the model in classic MVC.
Now MVC is often used to describe a whole web application framework, like in Microsofts Asp.net MVC framework.
Even then, some old timers continue to use the term MVC for a specific patten used when developing desktop GUI code. So in short, MVC can mean very different things depending on who you ask.