Is ClickHouse safe to use?

ClickHouse has an HVTrust score of 65.4/100 (Grade B), ranked #222 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for ClickHouse?

ClickHouse scores 65.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 846 GitHub stars and is categorized under MCP Servers.

ClickHouse

ClickHouse/mcp-clickhouse

Connect ClickHouse to your AI assistants.

MCP Servers Python Grade B Listed Apache-2.0

65.4/100

Rank #222 of 1283

Compare ClickHouse

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-05 · 7d ago

Recent change

Rank +1

Is ClickHouse safe? ClickHouse scores 65.4/100 (Grade B), ranked #222 of 1283 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; no OSSF Scorecard result yet; 81% of recent commits are signed; last pushed 2026-08-05. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#63 Intervals Icu MCP — 65.7 (B) → #64 Zigbee2MQTT MCP — 65.7 (B) → #66 Testrail MCP Server — 65.3 (B) → #67 Grafana MCP Server — 65.1 (B) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 17 spots (#203 → #220)

2026-08-08

Newly Listed

First tracked at rank #200

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

Compare with another agent Get email alerts for ClickHouse View MCP Servers Report missing data

62.0

Activity sub-score · out of 100

#65

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 →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

846

Forks

197

Last Push

2026-08-05

7 days ago

Commits (4 wk)

Downloads (7d)

46,873

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #221

Analysis

HVTrust Dimensions vs MCP Servers

65.4 / 100 · 100.0% confidence

ClickHouse MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

11.5 / 25

6.5 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

13.1 / 20

0.7 above avg 12.4

AdoptionLog-scaled stars · package downloads

13.3 / 20

7.5 above avg 5.8

Activity Inputs

62.0 / 100

StarsRepository reach

17.6 / 30

FreshnessLast push recency

24.0 / 25

ActivityRecent commits

9.7 / 25

CommunityFork signal

10.7 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

—

Not available

Signed Commits

81%

of last 100 commits verified

Is ClickHouse safe?

ClickHouse has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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?

No OpenSSF Scorecard data is currently published for ClickHouse. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is ClickHouse actively maintained?

Actively maintained. The repository was pushed to within the last 7 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?

80% 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

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

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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON