event-hog has its own repo, a README that says what it's for, and a page on the internet
The server moved out of a private stack into lossless-group/event-hog-mcp, with the kit, a license, a data policy, a CRM spec, and now a splash page that reads like a conference program.
Why Care?
event-hog worked the floor at the 7x24 Exchange Fall 2026 with Edviro Energy, and it worked. Now anyone can run it, read it, or fork it, and a CTO can check that it does what we say it does.
What’s New?
- Its own public repo. lossless-group/event-hog-mcp, extracted from a private stack with its history kept. Every deployment now sets its own address and ids.
- The kit ships with the server. Skills, the event template, and a generic settings example. No team’s real settings or people.
- A README that says what it’s for. Why it exists, what it does before, during and after an event, three ways to run it (no backend, Cloudflare Artifacts, paired with a CRM), and what the server guarantees versus what it only asks the model to do.
- COLLABORATE.md. How to fork, where to start a review, and the rule that no real event data goes in this repo.
- DATA-POLICY.md. On our deployment, a team’s data is stored so they can use it, and never looked at or used commercially. Draft, not yet reviewed by a lawyer.
- A CRM spec. Pick a CRM and Go: a team picks HubSpot, Twenty, or plain CSV once, and syncs with one preview and one approval.
- A splash page at lossless-group.github.io/event-hog-mcp, laid out as a conference: a lanyard badge, the program, three passes, and the workspace as a floor plan.
Licensed
Apache-2.0, with a NOTICE that credits The Lossless Group.