The current implementation of the MBS User Services API at reference point Nmb10 does not implement the HTTP GET method for the .../nmbsf-mbs-us/v1/mbs-user-services path (non-individual path).
This should return a JSON array of MBSUserService structures according to TS 29.580 Clause 6.1.3.2.3.1. This was likely missed in the initial implementation due to this operation not appearing in TS 29.580 Clause 5.2.
Note: The returned structure does not provide the mapping of the returned MBSUserService structures to their resource Id values for access via the individual MBS User Service API path. This is probably an oversight in TS 29.580. 5G-MAG/Standards#191 raises the issue of the missing resource Ids.