ClickHouse
PYPI · MCP-CLICKHOUSE · 2 COMPONENTS · SCANNED SEP 20
Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.
Available components
Recent critical change
CVE-2026-32871 affects this package (4 Aug 2026). See the changelog before you install this server.
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 27 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 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 420 tokens (~140/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run_query" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 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-clickhouse. 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-clickhouse
claude mcp add clickhouse-mcp-clickhouse -- uvx mcp-clickhouse
{
"mcpServers": {
"clickhouse-mcp-clickhouse": {
"command": "uvx",
"args": [
"mcp-clickhouse"
]
}
}
} {
"servers": {
"clickhouse-mcp-clickhouse": {
"command": "uvx",
"args": [
"mcp-clickhouse"
]
}
}
} codex mcp add clickhouse-mcp-clickhouse -- uvx mcp-clickhouse
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"clickhouse-mcp-clickhouse": {
"type": "local",
"command": [
"uvx",
"mcp-clickhouse"
],
"enabled": true
}
}
} openclaw mcp add clickhouse-mcp-clickhouse --command uvx --arg mcp-clickhouse
mcp_servers:
clickhouse-mcp-clickhouse:
command: "uvx"
args: ["mcp-clickhouse"] {
"McpServers": {
"clickhouse-mcp-clickhouse": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-clickhouse"
]
}
}
} assistant mcp add clickhouse-mcp-clickhouse -t stdio -c uvx -a mcp-clickhouse
{
"mcpServers": {
"clickhouse-mcp-clickhouse": {
"command": "uvx",
"args": [
"mcp-clickhouse"
]
}
}
} 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.
- 19 Sept 26 −2
- Stability: pass → 0.83 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 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.
- 12 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 11 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 8 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
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 20 Sept 2026 · Analysed pypi/mcp-clickhouse@0.6.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 27 packages
| Packages resolved | 27 |
|---|---|
| Stale | 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 →
list_databases List Databases ~15
List available ClickHouse databases
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_tables List Tables ~205
List available ClickHouse tables in a database, including schema, comment, row count, and column count. Integers outside [-9007199254740991, 9007199254740991] in table metadata are returned as decimal strings. Pagination tokens are single-use and retained for up to one hour.
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | yes | The database to list tables from |
| include_detailed_columns | boolean | – | Whether to include detailed column metadata (default: True). When False, the columns array will be empty but create_table_query still contains all column information. This reduces payload size for la… |
| like | – | – | Optional LIKE pattern to filter table names |
| not_like | – | – | Optional NOT LIKE pattern to exclude table names |
| page_size | integer | – | Number of tables to return per page (default: 50, must be greater than 0) |
| page_token | – | – | Single-use token from a previous call, retained for up to one hour |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
run_query Run Query ~136
Execute SQL queries in ClickHouse. Queries run in read-only mode by default. Set CLICKHOUSE_ALLOW_WRITE_ACCESS=true to allow DDL and DML operations. Set CLICKHOUSE_ALLOW_DROP=true to additionally allow destructive operations (DROP, TRUNCATE, DELETE, UPDATE, REPLACE TABLE/PARTITION, CREATE OR REPLACE, CLEAR COLUMN/INDEX/PROJECTION, DETACH PERMANENTLY). That gate is a best-effort accident guard, not a security boundary. Integers outside [-9007199254740991, 9007199254740991] are returned as decimal strings.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the ClickHouse MCP server?
ClickHouse is an MCP server listed in the public MCP registry as io.github.ClickHouse/mcp-clickhouse. Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB. This page covers its PyPI package (mcp-clickhouse).
Is the ClickHouse MCP server safe to use?
ClickHouse scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 3 tools: list_databases, list_tables, run_query. Their descriptions and schemas cost roughly 356 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.