Rendered at 23:18:05 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
blazarquasar 4 days ago [-]
Slopforking an already open, established, governed project to slap your name and fake trademark on it while making zero actual changes/improvements apart from renaming things and adding a Gandhi quote is definitely something. I hope that no one wastes their time on contributing here…
enclawed 7 hours ago [-]
Thank you for raising the concerns because this gives me a way to clarify several critical points about OMCP.
1) "Slopforking": While the MCP is open in the sense that you can read it, use it, copy it, and modify it pretty much however you like, its governance is closed and dictatorial. Their last move is that they closed many of the SEPs that were not pre-sponsored on Discord channel, without disclosing the acceptance rule for the SEPs that have been kept, and that now, before anybody can even open a SEP, they need the OK of a working group in the Discord channel [https://github.com/modelcontextprotocol/modelcontextprotocol...]. What they omitted or ignored to admit is that these authorized workgroups are often non-existent, leading to indefinitely long wait times and other inefficiencies that should not be there, and that everyone can get permanently banned from that Discord channel for no reason at all or because they feel like you are an AI agent or other amenities of sort. While there is an official route to recourse a ban, you may never get an answer or a decision on that at the sole discretion of the moderators, making it simply impossible to even propose something new or follow up on something already initiated.
OMCP solves that problem by removing the whole concept of non-engineering-based gatekeeping and kiss-the-ring policy, putting contribution quality back at the center.
Community-driven evaluation of each proposal to everyone. No ring-kissing the platinum members, no bureaucracy, no socialization. Nothing required except good, working code that solves a real problem that was previously unsolved. Testable, and documented.
2) "Fake trademark": The OMCP logo and text "OMCP" are original work copyright of Enclawed, Inc. and used as non-registered trademarks by Enclawed, Inc. 2026. Nothing fake there.
3) "Zero actual changes":
Everyone can independently verify the changes introduced by typing the following:
git clone https://github.com/enclawed/omcp && cd omcp
git remote add upstream https://github.com/modelcontextprotocol/modelcontextprotocol
git fetch upstream main && git diff --shortstat upstream/main HEAD
→ 397 files changed, 39,125 insertions, 17,742 deletions. 112 files added, 177 deleted, 105 modified (subject to change as the project is actively being developed).
4) On the Gandhi quote, my bad. I first heard that quote in the TV series "The Orville" and it was so poetic that I found it hard to believe they didn't copy it from somebody else. Online I found that it was Gandhi, but then on more thorough verification, turns out it was original from the Orville. It has been fixed.
5) "Waste of time": contributing to a project that gives the worldwide community a direct say on what the spec will look like, in my humble opinion, is far from a waste of time. But hey, don't use it if you don't like it. Freedom goes both ways.
1) "Slopforking": While the MCP is open in the sense that you can read it, use it, copy it, and modify it pretty much however you like, its governance is closed and dictatorial. Their last move is that they closed many of the SEPs that were not pre-sponsored on Discord channel, without disclosing the acceptance rule for the SEPs that have been kept, and that now, before anybody can even open a SEP, they need the OK of a working group in the Discord channel [https://github.com/modelcontextprotocol/modelcontextprotocol...]. What they omitted or ignored to admit is that these authorized workgroups are often non-existent, leading to indefinitely long wait times and other inefficiencies that should not be there, and that everyone can get permanently banned from that Discord channel for no reason at all or because they feel like you are an AI agent or other amenities of sort. While there is an official route to recourse a ban, you may never get an answer or a decision on that at the sole discretion of the moderators, making it simply impossible to even propose something new or follow up on something already initiated.
OMCP solves that problem by removing the whole concept of non-engineering-based gatekeeping and kiss-the-ring policy, putting contribution quality back at the center.
Community-driven evaluation of each proposal to everyone. No ring-kissing the platinum members, no bureaucracy, no socialization. Nothing required except good, working code that solves a real problem that was previously unsolved. Testable, and documented.
2) "Fake trademark": The OMCP logo and text "OMCP" are original work copyright of Enclawed, Inc. and used as non-registered trademarks by Enclawed, Inc. 2026. Nothing fake there.
3) "Zero actual changes": Everyone can independently verify the changes introduced by typing the following:
4) On the Gandhi quote, my bad. I first heard that quote in the TV series "The Orville" and it was so poetic that I found it hard to believe they didn't copy it from somebody else. Online I found that it was Gandhi, but then on more thorough verification, turns out it was original from the Orville. It has been fixed.5) "Waste of time": contributing to a project that gives the worldwide community a direct say on what the spec will look like, in my humble opinion, is far from a waste of time. But hey, don't use it if you don't like it. Freedom goes both ways.