chore(deps): update dependency mcp-clickhouse to v0.3.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
mcp-clickhouse	0.2.0 → 0.3.0

---

Release Notes

ClickHouse/mcp-clickhouse (mcp-clickhouse)

v0.3.0

Compare Source

Added

• SNI override support via CLICKHOUSE_SNI environment variable for connections behind proxies or load balancers. (#​127)
• Lazy-load chdb to avoid ~80-100 MB memory overhead when the feature is disabled. (#​144)
• Made chdb an optional dependency for Windows compatibility. (#​145)
• Optional write access mode via CLICKHOUSE_WRITE_ACCESS environment variable, with built-in DROP and TRUNCATE protection. (#​93)
• Client config override support through MCP Context session states, enabling dynamic connection switching at runtime. (#​115)
• Custom middleware injection via CLICKHOUSE_MCP_MIDDLEWARE environment variable for hooking into the MCP server lifecycle. Includes an example middleware module. (#​114)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[github-actions]

🔒 MCP Security Scan Results

✅ mcp-clickhouse

• Status: Passed
• Tools scanned: 3
• Result: No security issues detected

---

Summary: Scanned 1 MCP server(s), all passed security checks. ✅

[github-actions]

🛡️ Skill Security Scan Results

⚠️ No skills were scanned in this PR.

[rdimitrov]

@renovatebot rebase

[JAORMX]

Triage: build-containers blocked by genuine upstream CVEs

Local Grype scan (DB 2026-04-27) of the 0.3.0 image surfaces these HIGH/CRITICAL findings (severity-cutoff: high, only-fixed: true):

Package	Installed	GHSA	Severity	Fixed in
fastmcp	2.14.7	GHSA-vv7q-7jx5-f767	Critical	3.2.0
fastmcp	2.14.7	GHSA-rww4-4w9c-7733	High	3.2.0

These are genuine upstream CVEs in fastmcp, not false positives. The fix requires bumping fastmcp to 3.2.0, which is blocked by mcp-clickhouse's own constraint fastmcp<3.0.0,>=2.0.0.

Recommendation: Hold this bump until upstream ClickHouse/mcp-clickhouse widens its fastmcp constraint to allow 3.x.