Chmcp MCP Server

chmcp PyPI v0.1.2

Published by oualib — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A comprehensive Model Context Protocol (MCP) server for ClickHouse database operations and ClickHouse Cloud management.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

low Shell/command execution in packaging/dev tooling (scripts/test.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/test.py:22`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: result = subprocess.run(cmd, check=True) print(f"✅ {description} completed successfully")

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/test.py

Tools 55

Each tool and what it can reach — statically extracted from the published source.

  • cloud_create_api_keyno sensitive capability
  • cloud_create_clickpipeno sensitive capability
  • cloud_create_invitationno sensitive capability
  • cloud_create_query_endpoint_configno sensitive capability
  • cloud_create_reverse_private_endpointno sensitive capability
  • cloud_create_serviceno sensitive capability
  • cloud_create_service_private_endpointno sensitive capability
  • cloud_delete_api_keyno sensitive capability
  • cloud_delete_clickpipeno sensitive capability
  • cloud_delete_invitationno sensitive capability
Show 45 more tools ↓
  • cloud_delete_query_endpoint_configno sensitive capability
  • cloud_delete_reverse_private_endpointno sensitive capability
  • cloud_delete_serviceno sensitive capability
  • cloud_get_activityno sensitive capability
  • cloud_get_api_keyno sensitive capability
  • cloud_get_available_regionsno sensitive capability
  • cloud_get_backupno sensitive capability
  • cloud_get_backup_configurationno sensitive capability
  • cloud_get_clickpipeno sensitive capability
  • cloud_get_invitationno sensitive capability
  • cloud_get_memberno sensitive capability
  • cloud_get_organizationno sensitive capability
  • cloud_get_organization_metricsno sensitive capability
  • cloud_get_organization_private_endpoint_infono sensitive capability
  • cloud_get_private_endpoint_configno sensitive capability
  • cloud_get_query_endpoint_configno sensitive capability
  • cloud_get_reverse_private_endpointno sensitive capability
  • cloud_get_serviceno sensitive capability
  • cloud_get_service_metricsno sensitive capability
  • cloud_get_usage_costno sensitive capability
  • cloud_list_activitiesno sensitive capability
  • cloud_list_api_keysno sensitive capability
  • cloud_list_backupsno sensitive capability
  • cloud_list_clickpipesno sensitive capability
  • cloud_list_invitationsno sensitive capability
  • cloud_list_membersno sensitive capability
  • cloud_list_organizationsno sensitive capability
  • cloud_list_reverse_private_endpointsno sensitive capability
  • cloud_list_servicesno sensitive capability
  • cloud_remove_memberno sensitive capability
  • cloud_update_api_keyno sensitive capability
  • cloud_update_backup_configurationno sensitive capability
  • cloud_update_clickpipeno sensitive capability
  • cloud_update_clickpipe_scalingno sensitive capability
  • cloud_update_clickpipe_stateno sensitive capability
  • cloud_update_member_roleno sensitive capability
  • cloud_update_organizationno sensitive capability
  • cloud_update_serviceno sensitive capability
  • cloud_update_service_passwordno sensitive capability
  • cloud_update_service_replica_scalingno sensitive capability
  • cloud_update_service_scalingno sensitive capability
  • cloud_update_service_stateno sensitive capability
  • list_databasesno sensitive capability
  • list_tablesno sensitive capability
  • run_queryno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.2 latest A 99/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/chmcp/badge.svg)](https://mcptrustchecker.com/registry/chmcp)
HTML
<a href="https://mcptrustchecker.com/registry/chmcp"><img src="https://mcptrustchecker.com/registry/chmcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/chmcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan chmcp --online --registry pypi

Use the free API → How scoring works

More in Databases