Is ClickHouse safe to use?

ClickHouse has an HVTrust score of 84.1/100 (Grade A), ranked #95 of 1325 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 84.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 879 GitHub stars and is categorized under MCP Servers.

ClickHouse

ClickHouse/mcp-clickhouse

Connect ClickHouse to your AI assistants.

MCP Servers Python Listed Apache-2.0

Is ClickHouse safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.1 / 10

Provenance Attested

Signed commits 87%

Last push 5d ago

Compare ClickHouse

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: ClickHouse scores 84.1/100 (Grade A), ranked #95 of 1325 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 7.1/10; 87% of recent commits are signed; last pushed 2026-09-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How ClickHouse compares in MCP Servers

Bars show each HVTrust score; the tick marks ClickHouse’s 84.1.

Where the 84.1 comes from

HVTrust dimensions vs the MCP Servers average

84.1 / 100 · 100.0% confidence

ClickHouse MCP Servers average (775 agents)

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

20.7 / 25

10.4 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.5 / 17

2.3 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.8 / 20

4.7 above avg 12.1

AdoptionLog-scaled stars · package downloads

13.5 / 20

6.3 above avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

Maintainer Checklist

Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.

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

68.8

Activity sub-score · out of 100

#35

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 A 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-09-26

Activity & Reach

Stars

879

Forks

208

Last Push

2026-09-21

5 days ago

Commits (4 wk)

Downloads (7d)

66,485

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #93

Analysis

Activity Inputs

68.8 / 100

StarsRepository reach

17.7 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

15.9 / 25

CommunityFork signal

10.8 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

7.1 / 10

OpenSSF Scorecard · scanned Sep 21, 2026

Signed Commits

87%

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 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 8

Vulnerabilities 9

Common questions about ClickHouse

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 7.1/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 5 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?

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

How this surface has changed

Detected changes to ClickHouse's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

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-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 526 spots (#618 → #92)

2026-09-23

HVTrust Changed

HVTrust up 51.1pts (33.2 → 84.3)

2026-09-22

Newly Listed

First tracked at rank #618

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-05

Grade Changed

Trust grade B → A

2026-09-04

Rank Moved

Rank rose 28 spots (#127 → #99)

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

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