MVC is a descriptive point of view, not a prescriptive implementation plan. It's one of the only software idioms that's actually an Alexanderian Pattern, unlike the vast majority of the GoF that's just reflective of language warts/features.
There are tons of completely different ways you could describe the web as MVC:
Model View Controller
URL Response Request
DB Response Request
Response Hypermedia Sub-Requests
LocalStorage DOM Javascript
data:// JavaScript DOM Events
...For instance, events between M and V are pretty much required if you're doing it the "old way," but people tend to ignore that and just explicitly route messages through the C. The expression carries a lot less meaning now than it used to.
BTW I don't want to start a flame war about MVC. I just got some question marks about using a PHP 'MVC' framework.
Were it not for that I would be in complete agreement with you; I have absolutely no time for any framework that does not allow you to construct a mock request object, throw it into the controller, and verify correctness of the response object produced.