i don't know about the exact object you're looking for, it seems deprecated... you should maybe try other solutions like the sadam library and use the sadam.netReceive external, then decode the output using atoi fromsymbol regexp fromsymbol
it's boring, but it kind of works, maybe someone will have that object but...
@Patrick : as unsettling as it sounds, udpreceive doesn't work... i get this message using netsend :
udpreceive: OSC Bad message name string: DataAfterAlignedString: Unreasonably long string
Dropping entire message.
If i use CNMAT format and OpenSoundControl i get a DataAfterAlignedString: Unreasonably long string
though i get an osc packet (it prints FullPacket 8 639655792); OpenSoundControl doesn't seem to be able to decode this.
edit : and here's what printit says
printit: received MESSAGE "FullPacket" (0x238a56dc, s_thing 0x0) with 2 argument(s):
printit: LONG 8
printit: LONG 599960744
printit: It looks like an OSC packet
but the size is only 8 bytes, so I won't try to print it.
just to clarify :
Puredata [netsend] and [netreceive] objects are using FUDI protocol over tcp or udp (just as Pd itself internally to communicate between GUI and core).
Those are different from [tcpsend], [tcpreceive], [udpsend] or [udpreceive] (from mrpeach or iemnet lib) with which you can send or receive raw byte data from/in puredata.
Please see  for FUDI reference.
In Max, [udpreceive] and [udpsend] are using OSC at least since Max 5.0.8.
So I guess, it would have been more clear to call them [oscreceive] and [oscsend].
Or even [oscoverudpsend] [oscoverudpreceive], but I agree this is a long name for something that is simple to use.
So to replace the missing [netreceive] in Max, you have to use (since I can't find any alternative) the Sadam library.
And as it has been already said, put a [itoa] after it to convert the raw byte to human-readable messages.
But please note that I can't make it work in TCP, which is quite a pity since Pd is using it unless you tell it to use UDP.