ClickHouse
OCI · GHCR.IO/CLICKHOUSE/MCP-CLICKHOUSE:0.7.0 · 2 COMPONENTS
Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.
Available components
Last scanned (56 minutes ago)
Scores higher than 81% of OCI servers
Category Databases
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 44 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 635 tokens (~211/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Provenance: fail → unverified ▼ security
- 31 Oct 26 0
- Provenance: unverified → fail ▼ security
- 30 Oct 26 0
- Provenance: fail → unverified ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 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.
- 18 Oct 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.
- 16 Oct 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.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed oci/ghcr.io/clickhouse/mcp-clickhouse:0.7.0
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | oci |
| Reason | Attestation not fetched |
Background: How many MCP packages publish verified provenance →
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 ~351
Execute SQL queries in ClickHouse. Queries run in read-only mode by default. Bind optional params by name with {name:Type} placeholders, such as {name:String} or {vector:Array(Float32)}. Values may be JSON scalars, nulls, or arrays. Pass exact large integers as decimal strings. JSON lists and objects cannot bind to Tuple and Map types. Python percent formatting and $name$ raw binary parameters are not supported. Parameter values stay out of the MCP server's normal SQL log lines, but may appear in errors and backend logs. 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. Two optional checks also run through this tool. Use DESCRIBE (<query>) when you need a query's output columns and types; it inspects the result schema and surfaces analysis errors such as an unknown column, but a query that describes cleanly can still fail at runtime. Consider EXPLAIN ESTIMATE <query> before a SELECT that could be expensive; it returns the estimated parts, rows and marks read from MergeTree family tables, which is not run time and not result size. Neither runs the query body, though analysis can execute scalar subqueries.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the ClickHouse MCP server?
ClickHouse runs locally as a container image, launched with docker run --rm -i -e CLICKHOUSE_HOST -e CLICKHOUSE_USER -e CLICKHOUSE_PASSWORD -e CLICKHOUSE_PORT -e CLICKHOUSE_SECURE -e CLICKHOUSE_VERIFY -e CLICKHOUSE_CA_CERT -e CLICKHOUSE_CLIENT_CERT -e CLICKHOUSE_CLIENT_CERT_KEY -e CLICKHOUSE_TLS_MODE -e CLICKHOUSE_DATABASE -e CLICKHOUSE_ROLE -e CLICKHOUSE_ALLOW_WRITE_ACCESS -e CLICKHOUSE_ALLOW_DROP -e CLICKHOUSE_MCP_QUERY_TIMEOUT -e CLICKHOUSE_MCP_MAX_WORKERS ghcr.io/clickhouse/mcp-clickhouse:0.7.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/clickhouse/mcp-clickhouse:0.7.0
claude mcp add clickhouse-mcp-clickhouse -- docker run --rm -i -e CLICKHOUSE_HOST -e CLICKHOUSE_USER -e CLICKHOUSE_PASSWORD -e CLICKHOUSE_PORT -e CLICKHOUSE_SECURE -e CLICKHOUSE_VERIFY -e CLICKHOUSE_CA_CERT -e CLICKHOUSE_CLIENT_CERT -e CLICKHOUSE_CLIENT_CERT_KEY -e CLICKHOUSE_TLS_MODE -e CLICKHOUSE_DATABASE -e CLICKHOUSE_ROLE -e CLICKHOUSE_ALLOW_WRITE_ACCESS -e CLICKHOUSE_ALLOW_DROP -e CLICKHOUSE_MCP_QUERY_TIMEOUT -e CLICKHOUSE_MCP_MAX_WORKERS ghcr.io/clickhouse/mcp-clickhouse:0.7.0
This image reads CLICKHOUSE_HOST, CLICKHOUSE_USER, CLICKHOUSE_PASSWORD, CLICKHOUSE_PORT, CLICKHOUSE_SECURE, CLICKHOUSE_VERIFY, CLICKHOUSE_CA_CERT, CLICKHOUSE_CLIENT_CERT, CLICKHOUSE_CLIENT_CERT_KEY, CLICKHOUSE_TLS_MODE, CLICKHOUSE_DATABASE, CLICKHOUSE_ROLE, CLICKHOUSE_ALLOW_WRITE_ACCESS, CLICKHOUSE_ALLOW_DROP, CLICKHOUSE_MCP_QUERY_TIMEOUT and CLICKHOUSE_MCP_MAX_WORKERS. Set them in your client's env block for this server; docker run -e passes each one through to the container.
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 container image (ghcr.io/clickhouse/mcp-clickhouse:0.7.0).
Is the ClickHouse MCP server safe to use?
ClickHouse scores 51 out of 100 on VerifyMCP. 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 571 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ClickHouse MCP server under?
ClickHouse declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.