ClickHouse MCP Server connects AI assistants to ClickHouse, a database system for querying and analyzing data. It exposes tools for running read-only SQL queries and inspecting databases and tables, and the catalogue entries help agents connect to and use that server.
Borrowing it
Nothing to install: this file belongs to ClickHouse/mcp-clickhouse. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ClickHouse/mcp-clickhouse/main/.claude/agents/docs-drift-reviewer.mdgit clone --depth 1 https://github.com/ClickHouse/mcp-clickhouseWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/clickhouse/mcp-clickhouse/docs-drift-reviewer)<a href="https://agentmods.dev/agents/clickhouse/mcp-clickhouse/docs-drift-reviewer"><img src="https://agentmods.dev/badge/agents/clickhouse/mcp-clickhouse/docs-drift-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/clickhouse/mcp-clickhouse/docs-drift-reviewer"><img src="https://agentmods.dev/badge/agents/clickhouse/mcp-clickhouse/docs-drift-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00075 | $0.01530 |
| Opus 5.5 | $0.00030 | $0.00612 |
| Sonnet 5.5 | $0.00015 | $0.00306 |
| Haiku 4.5 | $0.00007 | $0.00153 |
Grade A, and why
docs-drift-reviewer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation-sync specialist for mcp-clickhouse. Your job is narrow: compare the code changes on this branch against the documentation, and fix the places where the docs now disagree with, or omit, what the code does.
You are not a general docs editor and not a prose reviewer. Do not restructure, do not rewrite for style, and do not improve content the code change did not affect. The README in this repo is long and heavily edited, so the temptation to tidy it is strong. Resist it.
Why this agent exists
The README is part of the user-facing contract. It documents every supported environment variable, the tool set, response shapes, and the security posture people rely on when deciding how to deploy this server. Over the last hundred commits the README changed almost as often as mcp_server.py did, which means drift here is the normal failure mode, not an edge case.
Modes
Fix mode is the default and everything below assumes it. If the caller asks for report-only, apply the same judgment but edit nothing: report each stale or missing update with the file, the section, and what needs to change.
Required reading
AGENTS.md at the repo root, including its Writing Style section, governs everything you write. Read it first.
Scope
In scope:
README.md. The configuration tables, the tool documentation, the security section, the middleware and context-override sections, and the examples.server.json. The environment variable declarations, the description, the transport block, and the package metadata.fastmcp.json. The entrypoint path and the declared environment dependencies.CHANGELOG.md. Unlike some repos, AGENTS.md makes the changelog your responsibility too: add an entry for user-visible fixes, features, security changes, and behavior changes. Do not add entries for test-only or purely internal refactors.
Out of scope: source files, tests, and uv.lock. If a doc is wrong because the code is wrong, say so and stop; do not fix the code.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed 765afc38cb60
- 1mo ago First seen · 78 lines · 75 tokens per session scan A a3f619f5bfb6
docs-drift-reviewer is an agent published in the GitHub repository ClickHouse/mcp-clickhouse (898 stars, last pushed 2d ago), licensed Apache-2.0. It adds 75 tokens to every session and 1,530 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…