head to head · open source
cadence vs vibe-check-mcp-server
cadence has 9,536 GitHub stars, 930 forks, 205 open issues and last shipped yesterday. vibe-check-mcp-server has 504 stars, 67 forks, 5 open issues and last shipped 4 days ago. cadence leads on adoption by 1,792% (9,536 vs 504 stars). cadence is written in Go under Apache-2.0; vibe-check-mcp-server is written in TypeScript under MIT. cadence has attracted 10% as many forks as stars, vibe-check-mcp-server 13%. cadence was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (workflow-automation), so they are genuine substitutes rather than adjacent tools.
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 20902 open source comparisons
Side by side
| cadence | vibe-check-mcp-server | |
|---|---|---|
| GitHub stars | ★ 9.5K | ★ 504 |
| License | Apache-2.0 | MIT |
| Written in | Go | TypeScript |
| Last push | 2026-11-04 | 2026-11-01 |
| Forks | ⑂ 930 | ⑂ 67 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick cadence if
- You weight community size — 9.5K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- 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 cadence
Cadence Cadence Workflow is an open source platform since 2017 for building and running scalable, fault tolerant, and long running workflows. This repository contains the core orchestration engine and tools including CLI, schema managment, benchmark and canary. Getting Started Cadence backend consists of multiple services, a database (Cassandra/MySQL/PostgreSQL) and optionally Kafka+Elasticsearch. As a user, you need a worker which contains your workflow implementation. Once you have Cadence backend and worker(s) running, you can trigger workflows by using SDKs or via CLI. 1. Start cadence backend components…
read the full cadence 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…
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 cadence or vibe-check-mcp-server more popular?
cadence has 9,536 GitHub stars and vibe-check-mcp-server has 504. cadence has the larger community by that measure.
Are cadence and vibe-check-mcp-server free?
Both are open source. cadence is licensed under Apache-2.0 and vibe-check-mcp-server under MIT. Neither carries a licence fee.
What is the difference between cadence and vibe-check-mcp-server?
cadence is written in Go 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, cadence or vibe-check-mcp-server?
Choose cadence if you want the larger community (9,536 stars) or its Apache-2.0 licence terms. Choose vibe-check-mcp-server if its feature set, stack or MIT licence fits better. Both are self-hostable.