Hacker News Reader

Comment by mdaniel | Hacker News Reader

How does this work? https://github.com/vantage-sh/vantage-mcp-server?tab=License...

That is extra weird when thinking about the audience who might be Vantage.sh users (and thus have the ability to create the read-only token mentioned elsewhere) but would almost certainly be using it from their workstation, in a commercial context. Sounds like you're trying to keep someone from selling your MCP toy and decided to be cute with the licensing text

View on HN

I'm just trying to understand licenses, but doesn't the choice of MIT contradict the inital "non-commercial purposes" as MIT says 'including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software' - Therefore, the non-commercial purposes is actually void and I can use the software to the limits of MIT defines? And because it is already MIT, they can relicense only future software but not this piece anymore?

IANAL but that is my understanding. I created an issue to get some clarification - https://github.com/vantage-sh/vantage-mcp-server/issues/31

The issue was initially closed with the following comment:

> Hey Dave, it is as it is stated. The MCP is published with dual licenses depending on your intent. > https://fossa.com/blog/dual-licensing-models-explained/

After further discussion on the ticket the license is now just MIT.

You have a couple problems that I can see:

One is the MIT license does not prohibit selling. And wrapping it in a "for non-commercial uses" clause creates a contradiction difficult, if not impossible to enforce.

So if I want to use the software I just have to create a fork on my home machine for non-commercial purposes, update the license to MIT only, and then the fork is mine to do with as I want commercially? What's even the point of this license?

Reply on news.ycombinator.com