Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.dockndevai/mcp-clickhouse

NPM · @DOCKNDEVAI/MCP-CLICKHOUSE

ClickHouse query & management for AI agents — SQL-classified read/write/destructive gating.

−2 this week 93 Trust /100

Last scanned (5 hours ago)

Scores higher than 96% of npm servers

Category Databases

Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to dockndevai/mcp-clickhouse). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 36 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 304 tokens (~33/item across 9 items; 9 tools + 0 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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 −2
    • Stability: pass → 0.83 functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 0
    • Stability: pass → 0.97 functional
  • 19 Oct 26 0
    • Stability: 0.97 → pass security
  • 18 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.

  • 16 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.

  • 14 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.

  • 13 Oct 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

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 npm/@dockndevai/mcp-clickhouse@0.3.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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo dockndevai/mcp-clickhouse
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/dockndevai/mcp-clickhouse/.github/workflows/release.yml@refs/tags/v0.3.0
Rekor log index 2999525023
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:a84ee12bdc3a37145499873a6b2723455df42a4f7602a59ac3bef0b0917184c19c96baab24d655239f68319481ae6bf4856fed79ba9bfc480cd827d2e

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~304 tokens

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 →

Tool Tokens
cluster_info ~22

Cluster topology from system.clusters (shards, replicas, hosts).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

describe_table ~39

Column names, types, defaults, and comments for a table.

NameTypeReqDescription
databasestringyesDatabase name
tablestringyesTable name

No output schema declared.

No examples provided.

list_databases ~15

List databases and their engines.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_tables ~31

List tables in a database with engine, row count, and size.

NameTypeReqDescription
databasestringyesDatabase name

No output schema declared.

No examples provided.

query ~62

Run a SELECT/SHOW/DESCRIBE query and return rows. Non-read statements are refused here — use `execute` (read-write mode) for those. Results are capped at CLICKHOUSE_MAX_ROWS.

NameTypeReqDescription
sqlstringyesA single read-only SQL statement

No output schema declared.

No examples provided.

running_queries ~24

Currently executing queries from system.processes (id, user, elapsed, memory).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

server_metrics ~23

Non-zero metrics from system.metrics (connections, merges, memory, etc.).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

show_create_table ~44

Return the full CREATE TABLE statement (schema, engine, settings) for a table.

NameTypeReqDescription
databasestringyesDatabase name
tablestringyesTable name

No output schema declared.

No examples provided.

table_stats ~44

Part count, row count, on-disk size, and time range from system.parts.

NameTypeReqDescription
databasestringyesDatabase name
tablestringyesTable name

No output schema declared.

No examples provided.

Install

How do I install the io.github.dockndevai/mcp-clickhouse server?

io.github.dockndevai/mcp-clickhouse runs locally as an npm package, launched with npx -y @dockndevai/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.

npm · @dockndevai/mcp-clickhouse

# add to Claude Code
claude mcp add dockndevai-mcp-clickhouse -- npx -y @dockndevai/mcp-clickhouse
Common questions

What is the io.github.dockndevai/mcp-clickhouse server?

io.github.dockndevai/mcp-clickhouse is listed in the public MCP registry as io.github.dockndevai/mcp-clickhouse. ClickHouse query & management for AI agents, SQL-classified read/write/destructive gating. This page covers its npm package (@dockndevai/mcp-clickhouse).

Is the io.github.dockndevai/mcp-clickhouse server safe to use?

io.github.dockndevai/mcp-clickhouse scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.dockndevai/mcp-clickhouse server expose?

io.github.dockndevai/mcp-clickhouse exposes 9 tools: list_databases, list_tables, describe_table, show_create_table, table_stats, and 4 more. Their descriptions and schemas cost roughly 304 tokens of context every time the server is loaded.

Is the io.github.dockndevai/mcp-clickhouse server still maintained?

io.github.dockndevai/mcp-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 io.github.dockndevai/mcp-clickhouse server under?

io.github.dockndevai/mcp-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.