updated 2026-09-04 22:32 UTC

ClickHouse

ClickHouse/mcp-clickhouse

Connect ClickHouse to your AI assistants.

MCP Servers Python Grade B Listed Apache-2.0
79.6/100
Rank #100 of 1320
Compare ClickHouse

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-04 · 0d ago
Recent change
Rank +1

Is ClickHouse safe? ClickHouse scores 79.6/100 (Grade B), ranked #100 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.0/10; 83% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#40 Sec Edgar MCP — 79.7 (B) → #41 Mikrotik MCP — 79.6 (B) → #43 Playwright MCP — 79.4 (B) → #44 Automox MCP Server — 79.3 (B) →

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-04
Rank Moved
Rank rose 27 spots (#127 → #100)
2026-08-31
Rank Moved
Rank dropped 12 spots (#107 → #119)
2026-08-26
Scorecard Added
OSSF Scorecard: 5.0/10
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent Get email alerts for ClickHouse View MCP Servers Report missing data
67.6
Activity sub-score · out of 100
#42
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 22:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
866
Forks
203
Last Push
2026-09-04
today
Commits (4 wk)
13
Downloads (7d)
46,873
pypi
HN mentions (30d)
—
Open Issues
7
Rank Change
▲27
was #127

Analysis

HVTrust Dimensions vs MCP Servers

79.6 / 100 · 100.0% confidence

ClickHouse MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.9 / 25
8.3 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
1.0 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
16.6 / 20
4.4 above avg 12.2
AdoptionLog-scaled stars · package downloads
13.3 / 20
7.0 above avg 6.3

Activity Inputs

67.6 / 100
StarsRepository reach
17.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
14.3 / 25
CommunityFork signal
10.7 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.0 / 10
OpenSSF Scorecard · scanned Sep 3, 2026
Signed Commits
83%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 5
CI-Tests 10
CII-Best-Practices 0
Code-Review 10
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is ClickHouse safe?

Public supply-chain signals for ClickHouse are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but ClickHouse carries less obvious unverified-evidence risk than projects with thin signals.
Does ClickHouse publish package provenance?
Yes. ClickHouse's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does ClickHouse have an OpenSSF Scorecard?
ClickHouse has an OpenSSF Scorecard score of 5.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is ClickHouse actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does ClickHouse use?
ClickHouse ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are ClickHouse's commits signed?
83% of the last 100 commits to ClickHouse are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
ClickHouse appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain ClickHouse?

For maintainers

HVTrust scores ClickHouse from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 11Grade 2Listed 1HVTrust 1Scorecard 1
2026-09-04
Rank Moved
Rank rose 27 spots (#127 → #100)
2026-08-31
Rank Moved
Rank dropped 12 spots (#107 → #119)
2026-08-26
Scorecard Added
OSSF Scorecard: 5.0/10
2026-08-26
Rank Moved
Rank rose 134 spots (#234 → #100)
2026-08-26
HVTrust Changed
HVTrust up 10.6pts (65.2 → 75.8)
2026-08-24
Rank Moved
Rank dropped 17 spots (#217 → #234)
2026-08-20
Grade Changed
Trust grade C → B
2026-08-20
Rank Moved
Rank rose 29 spots (#256 → #227)
2026-08-19
Rank Moved
Rank dropped 17 spots (#239 → #256)
2026-08-17
Rank Moved
Rank rose 11 spots (#249 → #238)
2026-08-16
Grade Changed
Trust grade B → C
2026-08-16
Rank Moved
Rank dropped 24 spots (#225 → #249)
2026-08-13
Rank Moved
Rank dropped 18 spots (#207 → #225)
2026-08-12
Rank Moved
Rank rose 14 spots (#221 → #207)
2026-08-10
Rank Moved
Rank dropped 17 spots (#203 → #220)
2026-08-08
Newly Listed
First tracked at rank #200
GitHub → PyPI: mcp-clickhouse

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 79.6 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/clickhouse.svg)](https://hvtracker.net/agents/clickhouse)
HTML:
<a href="https://hvtracker.net/agents/clickhouse"><img src="https://hvtracker.net/badge/clickhouse.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON