M-V-C is one of many "patterns" from the non-game software industry that folks sometimes apply to games.
Th general problem with such approaches is that they come from the non-game software industry, and may or may not be applicable to games.
MVC is a business app model as i recall.
Game software, otoh, is modeling and simulation software. so one would expect "patterns" from modeling and simulation to be applicable, and "patterns" from other types of software to be perhaps less so. if you want to think of the game's data as the model, render as the view, and process_input and update as the controller (or would update be part of the model? i'd have to look up MVC again), i see no major harm. as long as it doesn't lead to unnatural code organization, and therefore unnecessary complexity.
me personally, i'd stick with "patterns" that come from game development- such as the "main game loop" pattern! <g>.
or the "render all" pattern, or the "update all" pattern. or the "process_input" pattern. or the "entities list" pattern, or the "world/level map" pattern.
THESE are the "patterns" one sees in games, not stuff like MVC.