ClickHouse
PYPI · MCP-CLICKHOUSEX
Read-only MCP server for ClickHouse metadata, parameterized queries, and plan analysis.
Available components
Last scanned (5 hours ago)
Scores higher than 99% of PyPI 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 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 build step with no custom scripting around it. View diagnostics → Pass
- 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to alyiox/mcp-clickhousex). View diagnostics → Pass
- Clear OSI-approved license (MIT).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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 287 tokens (~71/item across 4 items; 3 tools + 1 resources), lean.Pass
- 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 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 23 Oct 26 +4
- Stability: fail → pass ▲ security
- 22 Oct 26 +15
- Malware scan: unverified → 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 5 Nov 2026 · Analysed pypi/mcp-clickhousex@0.11.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | alyiox/mcp-clickhousex |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/alyiox/mcp-clickhousex/.github/workflows/ci.yml@refs/tags/0.11.0 |
| Rekor log index | 2893920913 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:3afd4d5ec9e8f997f727da041c9af0ec8ef7c29648e85dad956d254c8bdf665c |
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 34 packages
| Packages resolved | 34 |
|---|---|
| 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 ~139
[ClickHouse] Explain read-only SELECT. Indexes names only the keys the plan used; confirm absent keys from system.tables (primary_key, sorting_key, partition_key).
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Session default database for unqualified names. Src: system.databases. |
| parameters | – | – | Named parameters for driver placeholders (e.g. %(name)s or {name:Type}). |
| profile | – | – | Profile name; default profile when omitted. Src: profiles. |
| sql | string | yes | Read-only SELECT to EXPLAIN. One statement. |
| types | – | – | EXPLAIN variants: plan (indexes), pipeline, syntax. Default plan and pipeline. |
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline | – | – | EXPLAIN PIPELINE output. |
| plan | – | – | EXPLAIN PLAN output. |
| syntax | – | – | EXPLAIN SYNTAX output. |
No examples provided.
list_profiles ~17
[ClickHouse] List configured connection profiles.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
run_query ~118
[ClickHouse] Execute read-only SELECT or SHOW.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | Session default database for unqualified names. Src: system.databases. |
| parameters | – | – | Named parameters for driver placeholders (e.g. %(name)s or {name:Type}). |
| profile | – | – | Profile name; default profile when omitted. Src: profiles. |
| snapshot | boolean | – | Spill the result to a CSV resource under a larger row cap, instead of returning rows inline. |
| sql | string | yes | One read-only statement: SELECT, WITH or SHOW. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | RFC 4180 CSV string: first row is the header, remaining rows are data. Absent when the result was spilled to snapshot_uri. |
| row_count | integer | yes | Number of data rows in the result. |
| row_limit | – | – | The enforced maximum number of rows returned for this query. |
| snapshot_uri | – | – | MCP resource URI for the snapshot CSV (e.g. ``chx://snapshots/{id}``). Fetch it via the snapshot resource. Entries expire after 7 days. Absent when rows were returned inline. |
| truncated | – | – | Whether the result set was truncated due to the enforced row limit. |
No examples provided.
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
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 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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_profiles, run_query, analyze_query. Their descriptions and schemas cost roughly 274 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 MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.