UML stereotype for marking remote objects

Is there a standard UML stereotype for marking remote objects (for example those who implement the Remote interface in Java).