not yet … Thanks for the tip, I’ll have a look as soon as UP works on my S7 (where my Molly-UP is) … because UP-Example (the test app provided by UP) doesn’t work on the S7 either (it does work on the 4a though). This leads me to conclude that there is some kind of general bug in the S7 UP-implementation OR something I have completely overlooked so far… (or both… 
Maybe others will report on how UP works for them and whether it works for Molly-UP ootb or not (who knows, maybe there´s even an instance of mollysocket available in the UP- implementation of eOS/murena), I hope there will be some howto or documentation soon…
edit: UP-Example works fine on S7 with an extra-install of ntfy which is odd
Now waiting for the next signal-message to come in and check whether my setup notifies me (setup = S7 + ntfy install + molly socket server defined in ntfy + Molly-UP
(system-integrated ntfy seemingly includes hardcoded (?) server settings etc. which means it is impossible to define a Molly socket… nice for other apps I guess but a pity for molly)
edit #2 (+2d): the above described setup works for Molly-UP on S7/herolte … even though Molly still claims to be “waiting for the test notification” - nevertheless: since then I got notifications for every incoming signal message!