I can't redesign your game for you but I can tell you to step back and consider the original premise of MVC.
What does your domain model consist of?
An array of card face values that represent a shuffled deck,
A score,
A list of high scores?
A count of matching attempts? (Not sure what the premise of the game is)
What does your view consist of?
A background
A deck
Some number of displayed cards
A scoreboard
Some buttons?
So the job of PureMVC is to help you get the data from the Model into the View and update the Model based on user interaction at the View.
The Card class you are torn about is probably a view component that displays certain data from the Model - specifically the face value of the card. So it must be informed of the data it is to present. A mediator would do this. When you click on the card, (perhaps to turn it over), the Mediator would listen for this event and in turn either update the Model or perhaps send a notification heard by another mediator or a command that needs to take some action, such as seeing if you clicked on the right card.
-=Cliff>