You are thinking like a developer. In reality that means that now they are responsible for it, if MarkMonitor messes something up they can use their relationship to all the registrars to fix the problem and MarkMonitor is on the hook in case anything goes wrong.

This is a better situation to be in than some internal tooling that failed to notify someone because it got forgotten after the developer left.