Why Yankees must seriously pursue Aroldis Chapman reunion in Red Sox trade

The New York Yankees are near the top of the American League East standings. New York has been a consistent contender over the years, but the ball club has not earned a World Series victory since 2009 — which feels like an eternity for the Yankees. They want to do everything they can to get the job done in the Fall Classic this year, and acquiring a veteran reliever such as Aroldis Chapman could help them accomplish the feat.

Will the Yankees consider trading with the Boston Red Sox for Chapman, though? After all, the rivals rarely make trades with one another. The fact of the matter is that the Red Sox are at the bottom of the American League East standings right now. Chapman has a mutual option for 2027, so he may be a half-season rental for any team that acquires him before the MLB trade deadline.

In the long run, trading with the Yankees could help the Red Sox. They would receive at least a couple of talented prospects for a 38-year-old closer who may not even stay with the Yankees past this season.

Meanwhile, the trade makes sense for New York. Chapman has experience pitching with the Yankees, so the big market element will not be a problem. While they will not love trading prospects to a rival, the Yankees are likely willing to do whatever it takes to win the World Series as soon as possible.

Yankees closer David Bednar has endured ups and downs with the team. Bringing in Chapman could take some pressure away from Bednar, who may find more success in an 8th inning role.

Will this potential trade between the Yankees and Red Sox come to fruition? If the Red Sox continue to struggle, they will likely at least listen to trade offers for Chapman. The Yankees could certainly consider reaching out and making an offer for the veteran closer.

Nothing is guaranteed but the Red Sox and Yankees may end up discussing an Aroldis Chapman-led trade.

The post Why Yankees must seriously pursue Aroldis Chapman reunion in Red Sox trade appeared first on ClutchPoints.