Nice hacking session :)

I agree that it would be goof to have good & refreshed MC api , which
comes with MC,
not separately.
I just dont know how it is possible today: MC implementation have
spread among multiple dialects,
and asking everyone to update and sync will be an organizational nightmare.
Which gets us back to the question that it was bad idea maintaining MC
as in-image tool instead of separate package, loadable
from public repository & maintained there.

I stumbled over following:

Goofy>>url: repoUrl username: username password: password
	"Creates a repository from the given URL"

	| repo url |
	(repoUrl beginsWith: 'ftp://') ifTrue:[
		url := repoUrl asUrl.
		repo := MCFtpRepository host: url authority directory: url
pathString allButFirst
					user: username password: password.
	] ifFalse:[
		repo := MCHttpRepository location: repoUrl user: username password: password.
	].
	^self repository: repo.

this could be nicely repaced just by:

MCRepository location: url user: username password: password.

which then dispatch to its subclasses to find appropriate repo class
based on url schema.

-- 
Best regards,
Igor Stasenko AKA sig.