ch-ui vs MC-Data Monitor
ch-ui is a plugin bundle for AI coding tools published by Caio Ricciuti. Marketplaces we read that list it: 1 (Community GitHub marketplaces). MC-Data Monitor is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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 |  ch-ui | |
|---|---|---|
| Community marketplace caioricciuti/ch-ui | Listed Version: 1.0.0 Forks (GitHub): 72 Stars (GitHub): 726 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 | ch-ui | MC-Data Monitor |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 726 | No figure on GitHub |
| Forks (GitHub) (differs) | 72 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mc-data-monitor-mcp.vercel.app/api/mcp) |
| Transport (differs) | Not stated | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/caioricciuti/ch-ui | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 14 h ago |
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
ch-ui
CH-UI MCP server connection plus a ClickHouse analytics skill.
MC-Data Monitor
SQL pipeline observability and DBT integration monitor.
How to run each
ch-ui As a Claude Code plugin
/plugin marketplace add caioricciuti/ch-ui
/plugin install ch-ui@ch-uiMC-Data Monitor As a remote MCP server
claude mcp add --transport sse mc-data-monitor https://mc-data-monitor-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only MC-Data Monitor has a remote endpoint we 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: ch-ui · What it can do: MC-Data Monitor · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.