Chip MCP vs Vibe Coding Control
Chip MCP is an MCP server published by chip-ai.digital. Marketplaces we read that list it: 1 (Official MCP Registry). Vibe Coding Control is an MCP server published by OMNOM-111. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Chip MCP |   Vibe Coding Control |
|---|---|---|
| Official MCP Registry | Listed Version: 1.3.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Chip MCP | Vibe Coding Control |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Remote server (chip-ai.digital/mcp) | Remote server (vibecodingcontrol.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/zapret-digital/chip-mcp | github.com/omnom-111/vcc-remote |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | Responded 33 h ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Chip MCP
Project memory, tasks and Telegram notifications for your coding agent. Chip account required.
Vibe Coding Control
Your VCC projects, tasks, AI development history and owner decisions. Sign in with your VCC account.
How to run each
Chip MCP As a remote MCP server
claude mcp add --transport http chip https://chip-ai.digital/mcp/Vibe Coding Control As a remote MCP server
claude mcp add --transport http vcc-remote https://vibecodingcontrol.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Chip MCP · What it can do: Vibe Coding Control · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.