com.orgbix/site vs ClickHouse
com.orgbix/site is an MCP server published by orgbix.com. Marketplaces we read that list it: 1 (Official MCP Registry). ClickHouse is an MCP server published by ClickHouse. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, PyPI (MCP servers)). As of our marketplace pass on 2026-10-24. 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 |  com.orgbix/site |  ClickHouse |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 No figure published Not marked · First seen |
Listed Version: 0.7.0 Downloads/month (PyPI): 240 897 Downloads/week (PyPI): 61 608 Forks (GitHub): 210 Stars (GitHub): 892 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:51bcd33e17ad Forks (GitHub): 210 Pulls (Docker Hub): 373 514 Stars (Docker Hub): 3 Stars (GitHub): 892 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.7.0 Downloads/month (PyPI): 240 897 Downloads/week (PyPI): 61 608 Forks (GitHub): 210 Stars (GitHub): 892 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 | com.orgbix/site | ClickHouse |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 892 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 373 514 |
| Forks (GitHub) (differs) | No figure on GitHub | 210 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (orgbix.com/mcp) | On your machine (mcp-clickhouse) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | Not published | 3 |
| Environment variables it asks for (differs) | Not published | 16, secrets among them: 1 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | Not stated | github.com/clickhouse/mcp-clickhouse |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 26 h ago | no remote endpoint we check |
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
com.orgbix/site
Orgbix: the site's own MCP server — dataset; every answer cites the site.
ClickHouse
Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.
How to run each
com.orgbix/site As a remote MCP server
claude mcp add --transport http site https://orgbix.com/mcpClickHouse As a local MCP server: PyPI package
claude mcp add --env "CLICKHOUSE_HOST=<YOUR_CLICKHOUSE_HOST>" --env "CLICKHOUSE_PASSWORD=<YOUR_CLICKHOUSE_PASSWORD>" --env "CLICKHOUSE_USER=<YOUR_CLICKHOUSE_USER>" --transport stdio mcp-clickhouse -- uvx mcp-clickhouseRequires: CLICKHOUSE_HOST, CLICKHOUSE_PASSWORD (secret), CLICKHOUSE_USER
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.orgbix/site has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of com.orgbix/site publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of com.orgbix/site publish no settings it asks for, so we do not compare settings.
What it can do: com.orgbix/site · What it can do: ClickHouse · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.