head to head · open source
frigate vs vibe-check-mcp-server
frigate has 35,953 GitHub stars, 3,602 forks, 95 open issues and last shipped today. vibe-check-mcp-server has 503 stars, 66 forks, 5 open issues and last shipped 7 days ago. frigate leads on adoption by 7,048% (35,953 vs 503 stars). frigate is written in TypeScript under MIT; vibe-check-mcp-server is written in TypeScript under MIT. frigate has attracted 10% as many forks as stars, vibe-check-mcp-server 13%. frigate was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 8884 open source comparisons
Side by side
| frigate | vibe-check-mcp-server | |
|---|---|---|
| GitHub stars | ★ 36K | ★ 503 |
| License | MIT | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-09-18 | 2026-09-11 |
| Forks | ⑂ 3.6K | ⑂ 66 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick frigate if
- You weight community size — 36K stars and counting
- You want the MIT license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
pick vibe-check-mcp-server if
- You want the vibe-check-mcp-server feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and vibe-check-mcp-server fits your workflow better
About frigate
Frigate NVR is a complete and local network video recorder built for Home Assistant, with AI object detection. It uses OpenCV and Tensorflow to run realtime object detection locally on IP cameras, so video analysis happens on your own hardware instead of a vendor cloud. Project lives in the Home Assistant home automation ecosystem, with tight integration through a custom component, and it talks over MQTT so other systems can consume its events. Written mainly in TypeScript, MIT licensed, 8 years old, 35,896 stars and 3,596 forks on GitHub.
read the full frigate overview →
About vibe-check-mcp-server
Vibe Check MCP This project is in maintenance mode. Active feature development has ended; only maintenance patches (security and bug fixes) are published. v2.9.0 is the latest maintenance release. The server remains fully functional. Community forks and contributions are welcome under the MIT license. KISS overzealous agents goodbye. Plug & play agent oversight tool. Based on research: In our study agents calling Vibe Check improved success +27% and halved harmful actions 41% Featured on PulseMCP “Most Popular (This Week)” • 5k+ monthly calls on Smithery.ai • research backed oversight • STDIO + streamable HTTP tr…
read the full vibe-check-mcp-server overview →
More in Productivity & Utilities
Related comparisons
More Automation projects
Compare either of these against the rest of the Automation field.
Frequently asked questions
Is frigate or vibe-check-mcp-server more popular?
frigate has 35,953 GitHub stars and vibe-check-mcp-server has 503. frigate has the larger community by that measure.
Are frigate and vibe-check-mcp-server free?
Both are open source. frigate is licensed under MIT and vibe-check-mcp-server under MIT. Neither carries a licence fee.
What is the difference between frigate and vibe-check-mcp-server?
frigate is written in TypeScript and vibe-check-mcp-server in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, frigate or vibe-check-mcp-server?
Choose frigate if you want the larger community (35,953 stars) or its MIT licence terms. Choose vibe-check-mcp-server if its feature set, stack or MIT licence fits better. Both are self-hostable.