McKinsey does not publish a universal public passing score that candidates can reliably use across offices and recruiting cycles.

Assessment results can be considered alongside other parts of the application, and the format or scoring approach can change over time. That is why unofficial cutoffs should be treated cautiously.

If your version provides a score or decile, use it as feedback on your performance rather than assuming one number guarantees an interview.

The most productive target is strong, consistent performance across the tasks you are given. Focus on accuracy, decision quality and pacing instead of trying to reverse-engineer a hidden threshold. For more detail, see the McKinsey Solve scoring guide and the complete McKinsey Solve guide.

Rumored cutoffs stressed me out more than they helped.

I'd rather optimize for accuracy and pacing than chase a number nobody can verify.

This sounds like one of those questions where the specific office or school process matters more than the broad rule. In my case, the exact timing around what mckinsey solve score do i need to pass mattered most.