That's one of the problems with the idea of such an optional not-integrated type checker, compared to a type system.
Untyped values can freely change its types during runtime, typed variables not. Its fundamental safety mypy is violating here. types are giving a strong guarantee here. Only untyped const variables may be inferred.
Furthermore 3 more fundamental type system features are missing:
1) Typed variables can be unboxed if it makes sense for the compiler. at compile-time, not run-time.
2) some loop counters can be checked against array indices at compile-time, run-time oob checks can be omitted then.
3) the ffi needs types to be integrated. you can even layout structs in native classes as expected in C, completely unboxed. which is about 4x smaller and faster to use. and much easier to use.
type checking only is only about a third of a real type system. I've implemented a proper type system in cperl, and worked happily also with perl6 and other integrated gradual type systems, mypy and similar systems for other languages seem like a joke to me. a hint is something different than a guarantee.