clickhouse-monitoring vs Data Observability
clickhouse-monitoring is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
clickhouse-monitoring is a plugin bundle for AI coding tools published by duyet. No marketplace we read lists it any more. Data Observability is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace duyet/codex-claude-plugins | Removed on 2026-10-20 Version: 1.1.1 Forks (GitHub): 1 Stars (GitHub): 15 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 | clickhouse-monitoringno longer listed · | Data Observability |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 15 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (data-observability-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) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/duyet/codex-claude-plugins | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-25 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of clickhouse-monitoring
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
mcp-clickhouse io.github.infoinlet-marketplace/mcp-clickhouse
Read-only ClickHouse for AI agents — analytics queries, table inspection, sizes, health.
-
Connect Claude to your ClickHouse Cloud databases. Browse organizations, services, databases, and table schemas. Run read-only SQL queries against your data and get instant…
-
Read-only ClickHouse monitoring and advice through the chmonitor MCP server, with pointers to its docs and codebase.
-
Browse, query, and administer your managed WaveHouse + ClickHouse projects (schema, pipes, policy).
-
Enable AI agents to manage, monitor, and query CockroachDB using natural language. Perform complex database operations, cluster management, and query execution seamlessly through…
-
ClickHouse review rules for schemas, queries, and inserts, with references for debugging and monitoring queries.
What each says it does
clickhouse-monitoring
Agent Skill for the ClickHouse Monitor dashboard - a real-time monitoring and observability tool. Covers 45 dashboard pages including query monitoring, table management, merge operations, system metrics, security logs, and API integration.
Data Observability
SQL data health analyzer and pipeline observability evaluator.
How to run each
clickhouse-monitoring
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Data Observability As a remote MCP server
claude mcp add --transport sse data-observability https://data-observability-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 Data Observability 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: clickhouse-monitoring · What it can do: Data Observability · 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.