Check the requirements for stumping
The MCC 2026 code requires a delivered ball that is not a no-ball, a striker outside their ground who has not attempted a run, and a wicket fairly broken by the wicketkeeper without another fielder intervening. These conditions explain why the location of the batter and the identity of the fielder matter together.
A wide does not prevent those conditions being satisfied. Law 39.4 says the one-run wide penalty stands when the striker is dismissed stumped from a wide. There is an important result boundary: if that wide penalty itself concludes the match, a subsequent stumping cannot occur. The winning extra has already ended the match.
Do not relabel a protected no-ball incident
Law 39 does not allow a stumping from a no-ball. Law 38.2.2.2 also protects the striker from run out when the delivery is a no-ball, the striker is outside their ground without attempting a run, and the keeper breaks the wicket without another fielder’s intervention. The code has separate provisions where a batter has a runner.
The keeper removing the bails is consequently insufficient evidence on its own. Follow the delivery call, whether a run was attempted, and whether another fielder intervened. If the situation falls outside that exception, the full run-out law still needs to be applied; it is not an automatic dismissal either.
Keep enough of the replay to see the context
The batter’s movement can distinguish an attempted run from simply advancing to play a stroke. Leaving the ground to avoid injury also has express protections in the dismissal laws. A tight crop showing only the bails and a raised foot can omit facts needed for the decision.
Use the MCC edition and the event’s actual playing conditions together, especially when reviewing an older match. This explanation is based on the current primary code checked on 4 November 2026. It explains how to read the incident and official decision; it does not claim an independent adjudication of unseen footage.