Vibe Core vs PayMCP
Side-by-side comparison of two Model Context Protocol servers. Pick the right one for Claude Desktop, Claude Code, or Cursor.
Shared spine for the Vibe Suite: model-preference cascade (agent config → your key → on-device), cross-harness hooks, and the consent ledger that enforces local
Comparison
| Feature | Vibe Core | PayMCP |
|---|---|---|
| Pricing | Free | Free |
| Installs | — | 2 |
| Rating | — | — |
| Verified | — | |
| Hosted | — | — |
| Tools | — | — |
| Category | development | development |
| Author | pooriaarab | blustAI |
| Repo | pooriaarab/vibe-core | blustAI/paymcp |
When to pick Vibe Core
Shared spine for the Vibe Suite: model-preference cascade (agent config → your key → on-device), cross-harness hooks, and the consent ledger that enforces local-first.
When to pick PayMCP
Lightweight payments layer for MCP servers: turn tools into paid endpoints with a two-line decorator. [PyPI](https://pypi.org/project/paymcp/) · [npm](https://www.npmjs.com/package/paymcp) · [TS repo](https://github.com/blustAI/paymcp-ts)
Looking for something else? Browse all MCPs or check trending this week.