ClickHouse
PYPI · MCP-CLICKHOUSEX · SCANNED SEP 13
Read-only MCP server for ClickHouse metadata, parameterized queries, and plan analysis.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 35 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 45 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 892 tokens (~99/item across 9 items; 8 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the ClickHouse MCP server?
ClickHouse runs locally as a PyPI package, launched with uvx mcp-clickhousex. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-clickhousex
claude mcp add alyiox-mcp-clickhousex -- uvx mcp-clickhousex
{
"mcpServers": {
"alyiox-mcp-clickhousex": {
"command": "uvx",
"args": [
"mcp-clickhousex"
]
}
}
} {
"servers": {
"alyiox-mcp-clickhousex": {
"command": "uvx",
"args": [
"mcp-clickhousex"
]
}
}
} codex mcp add alyiox-mcp-clickhousex -- uvx mcp-clickhousex
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"alyiox-mcp-clickhousex": {
"type": "local",
"command": [
"uvx",
"mcp-clickhousex"
],
"enabled": true
}
}
} openclaw mcp add alyiox-mcp-clickhousex --command uvx --arg mcp-clickhousex
mcp_servers:
alyiox-mcp-clickhousex:
command: "uvx"
args: ["mcp-clickhousex"] {
"McpServers": {
"alyiox-mcp-clickhousex": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-clickhousex"
]
}
}
} assistant mcp add alyiox-mcp-clickhousex -t stdio -c uvx -a mcp-clickhousex
{
"mcpServers": {
"alyiox-mcp-clickhousex": {
"command": "uvx",
"args": [
"mcp-clickhousex"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 −3
- Stability: pass → 0.80 functional
- 3 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 13 Sept 2026 · Analysed pypi/mcp-clickhousex@0.9.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 35 packages
| Packages resolved | 35 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_query ~163
[ClickHouse] Explain read-only SELECT or WITH … SELECT. Returns plan, pipeline, and/or syntax text. Default types plan and pipeline. Uses query timeout and optional database; no max-rows cap unlike run_query.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Session default database for unqualified names. Src: databases. |
| parameters | – | – | Named parameters for driver placeholders (e.g. %(name)s or {name:Type}). |
| profile | – | – | Profile name; uses default profile when omitted. Src: profiles. |
| sql | string | yes | Read-only SELECT or WITH … SELECT for EXPLAIN. One statement; same validation as run_query. |
| types | – | – | EXPLAIN variants: plan (indexes), pipeline, syntax. Default plan and pipeline if omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline | – | – | EXPLAIN PIPELINE output. |
| plan | – | – | EXPLAIN PLAN output. |
| syntax | – | – | EXPLAIN SYNTAX output. |
No examples provided.
get_cluster_properties ~55
[ClickHouse] Get cluster properties and execution limits. Returns ClickHouse server version plus enforced limits (max rows, timeouts) for the profile.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | – | – | Profile name; uses default profile when omitted. Src: profiles. |
| Name | Type | Req | Description |
|---|---|---|---|
| limits | – | yes | – |
| version | string | yes | ClickHouse server version string. |
No examples provided.
list_columns ~94
[ClickHouse] List columns for a table or view. Rows from system.columns for the resolved database and table.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Database when table is unqualified; ignored if table contains a dot. Client default when omitted. Src: databases. |
| profile | – | – | Profile name; uses default profile when omitted. Src: profiles. |
| table | string | yes | Table or view name, or database.table. Src: tables. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | Ordered list of column names. Each row aligns with these names by index. |
| rows | array | yes | Row values aligned with the columns list. |
No examples provided.
list_databases ~43
[ClickHouse] List databases. Rows from system.databases visible to the connection.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | – | – | Profile name; uses default profile when omitted. Src: profiles. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | Ordered list of column names. Each row aligns with these names by index. |
| rows | array | yes | Row values aligned with the columns list. |
No examples provided.
list_profiles ~24
[ClickHouse] List configured profiles. Each entry includes name and optional description.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_tables ~81
[ClickHouse] List tables and views in a database. Rows from system.tables: name, engine, primary_key, sorting_key, partition_key, total_rows, total_bytes for query planning.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Database to list; client default when omitted. Src: databases. |
| profile | – | – | Profile name; uses default profile when omitted. Src: profiles. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | Ordered list of column names. Each row aligns with these names by index. |
| rows | array | yes | Row values aligned with the columns list. |
No examples provided.
run_query ~279
[ClickHouse] Execute read-only SELECT or WITH … SELECT. One statement; DML, DDL, SET, SYSTEM, and similar are rejected. Max-rows cap; overflow sets truncated and row_limit. Same SQL validation as analyze_query. Returns ``{data, row_count}`` where ``data`` is an RFC 4180 CSV string. Pass ``snapshot=true`` to persist the result to disk and receive a ``{snapshot_uri, row_count}`` instead; fetch the CSV via the snapshot resource URI.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Session default database for unqualified names. Src: databases. |
| parameters | – | – | Named parameters for driver placeholders (e.g. %(name)s or {name:Type}). |
| profile | – | – | Profile name; uses default profile when omitted. Src: profiles. |
| snapshot | boolean | – | When true, persist the full result as a CSV file and return a resource URI (chx://snapshots/{id}) instead of inline data. Use for queries that may exceed the interactive row limit (1 000). Snapshot l… |
| sql | string | yes | Read-only SELECT or WITH … SELECT. One statement; use qualified db.table or database. Driver placeholder syntax for parameters. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
run_show ~133
[ClickHouse] Execute SHOW introspection statement. One statement per call; INTO OUTFILE rejected. Interactive row limits apply (default 500, hard ceiling 1 000). Same timeout as run_query.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Session default database for unqualified names. Src: databases. |
| parameters | – | – | Named parameters for driver placeholders (e.g. %(name)s or {name:Type}). |
| profile | – | – | Profile name; uses default profile when omitted. Src: profiles. |
| sql | string | yes | Single SHOW statement (e.g. SHOW DATABASES, SHOW CREATE TABLE). No INTO OUTFILE. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | Ordered list of column names. Each row aligns with these names by index. |
| row_limit | – | – | The enforced maximum number of rows returned for this query. |
| rows | array | yes | Row values aligned with the columns list. |
| truncated | – | – | Whether the result set was truncated due to the enforced row limit. |
No examples provided.
What is the ClickHouse MCP server?
ClickHouse is an MCP server listed in the public MCP registry as io.github.alyiox/mcp-clickhousex. Read-only MCP server for ClickHouse metadata, parameterized queries, and plan analysis. This page covers its PyPI package (mcp-clickhousex).
Is the ClickHouse MCP server safe to use?
ClickHouse scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 13 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ClickHouse MCP server expose?
ClickHouse exposes 8 tools: list_profiles, get_cluster_properties, run_query, run_show, analyze_query, and 3 more. Their descriptions and schemas cost roughly 872 tokens of context every time the server is loaded.
Is the ClickHouse MCP server still maintained?
ClickHouse is still listed as active in the MCP registry. We last reached this channel on 13 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.