ToolsMCP
ClickHouse
Listed in the official MCP Registry with an installable pypi package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- alyiox (GitHub)
- Prerequisites
- Install mcp-clickhousex from pypi (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.11.0 · updated
- Official links
Publisher’s description
Read-only MCP server for ClickHouse metadata, parameterized queries, and plan analysis.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.11.0, registry status active. 1 package (pypi)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- alyiox (GitHub)
- Version observed
- 0.11.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.alyiox%2Fmcp-clickhousex/versions/0.11.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Query a database in plain language | Publisher description mentions “clickhouse”, “read-only”, “queries”. | No connection check or task run. Capability is as described by the publisher. | Rule database-query matched: “clickhouse”, “read-only”, “queries”. Rule database-query. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
mcp-clickhousex(pypi, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.alyiox/mcp-clickhousex
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.