On muscbrainz.org you can access the webservice as

http://musicbrainz.org/ws/2 ....

and the search service that the webservice uses for searches directly as ..

http://search.musicbrainz/ws/2

I require the service to be exposed in the VM as well (it currently is not) for two reasons

1. It allows access to some search server options that are not exposed via the webservice
2. I can use it to remove rate limiting on search internally enforced by Jaikoz/SongKong. (If musicbrainz url is local vm I remove rate limiting on webservice lookups and browse requests, however unless they have created local search indexes the local server still uses musicbrainz.org for searches, to disable rate limiting on search I require the user to enter search url which is different to musicbrainz url but this is not possible in the new Musicbrainz Vm.)