ClickHouse vs Peeringdb
ClickHouse is an MCP server published by ClickHouse. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, PyPI (MCP servers)). Peeringdb is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-31. 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 |  ClickHouse |  Peeringdb |
|---|---|---|
| Official MCP Registry | Listed Version: 0.7.0 Downloads/month (PyPI): 240 897 Downloads/week (PyPI): 61 608 Forks (GitHub): 210 Stars (GitHub): 899 Not marked · First seen |
Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:51bcd33e17ad Forks (GitHub): 210 Pulls (Docker Hub): 387 593 Stars (Docker Hub): 3 Stars (GitHub): 899 Not marked · First seen |
Not listed |
| PyPI (MCP servers) | Listed Version: 0.7.0 Downloads/month (PyPI): 240 897 Downloads/week (PyPI): 61 608 Forks (GitHub): 210 Stars (GitHub): 899 Not marked · First seen |
Not listed |
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 | Peeringdb |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 899 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 387 593 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 210 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | On your machine (mcp-clickhouse) | Remote server (gateway.pipeworx.io/peeringdb/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 16, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/clickhouse/mcp-clickhouse | github.com/pipeworx-io/mcp-peeringdb |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days 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
ClickHouse
Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.
Peeringdb
PeeringDB MCP — the peering ecosystem database. Look up networks by name or ASN, find internet…
How to run each
ClickHouse 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
Peeringdb As a remote MCP server
claude mcp add --transport http peeringdb https://gateway.pipeworx.io/peeringdb/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Peeringdb has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Peeringdb publish no list of tools, so we do not compare tools.
Settings each asks for
Only ClickHouse asks for
CLICKHOUSE_ALLOW_DROPCLICKHOUSE_ALLOW_WRITE_ACCESSCLICKHOUSE_CA_CERTCLICKHOUSE_CLIENT_CERTCLICKHOUSE_CLIENT_CERT_KEYCLICKHOUSE_CONNECT_TIMEOUTCLICKHOUSE_DATABASECLICKHOUSE_HOSTCLICKHOUSE_MCP_MAX_WORKERSCLICKHOUSE_MCP_QUERY_TIMEOUTCLICKHOUSE_PASSWORD (secret)CLICKHOUSE_PORT
Show the remaining 6
CLICKHOUSE_ROLECLICKHOUSE_SECURECLICKHOUSE_SEND_RECEIVE_TIMEOUTCLICKHOUSE_TLS_MODECLICKHOUSE_USERCLICKHOUSE_VERIFY
Only Peeringdb asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: ClickHouse · What it can do: Peeringdb · 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.