Mcp Clickhouse vs EOSL.ai — Hardware En… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mcp Clickhouse vs EOSL.ai — Hardware End Of Life Database
In-depth architectural comparison of the Mcp Clickhouse and EOSL.ai — Hardware End Of Life Database MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Mcp Clickhouse
Databases · Local stdio
Quality: 67/100 (Great) | Auth: API Key required
EOSL.ai — Hardware End Of Life Database
Databases · Remote HTTP/SSE
Quality: 54/100 (Good) | Auth: No auth required
Verdict Summary: Choose Mcp Clickhouse if you need specialized Databases tools running via a local process. Choose EOSL.ai — Hardware End Of Life Database if your workspace requires Databases integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Mcp Clickhouse when:
You need dedicated capabilities in the Databases domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: CLICKHOUSE_ALLOW_WRITE_ACCESS, CLICKHOUSE_MCP_AUTH_TOKEN, CLICKHOUSE_MCP_AUTH_DISABLED, FASTMCP_SERVER_AUTH, FASTMCP_SERVER_AUTH_AZURE_TENANT_ID, FASTMCP_SERVER_AUTH_AZURE_CLIENT_ID, FASTMCP_SERVER_AUTH_AZURE_CLIENT_SECRET.
List available ClickHouse tables in a database, including schema, comment,
row count, and column count.
Args:
database: The database to list tables from
like: Optional LIKE pattern to filter table names
not_like: Optional NOT LIKE pattern to exclude table names
page_token: Token for pagination, obtained from a previous call
page_size: Number of tables to return per page (default: 50)
include_detailed_columns: Whether to include detailed column metadata (default: True).
When False, the columns array will be empty but create_table_query still contains
all column information. This reduces payload size for large schemas.
Returns:
A JSON-encoded string of an object containing:
- tables: List of table information (as dictionaries)
- next_page_token: Token for the next page, or None if no more pages
- total_tables: Total number of tables matching the filters
run_query
Execute SQL queries in ClickHouse. Queries run in read-only mode by default. Set CLICKHOUSE_ALLOW_WRITE_ACCESS=true to allow DDL and DML operations. Set CLICKHOUSE_ALLOW_DROP=true to additionally allow destructive operations (DROP, TRUNCATE).
EOSL.ai — Hardware End Of Life Database Tools (5)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Mcp Clickhouse is categorized under Databases and uses a local stdio subprocess. In contrast, EOSL.ai — Hardware End Of Life Database belongs to Databases using remote streaming HTTP/SSE transport. Select Mcp Clickhouse when you need capabilities focused on databases and EOSL.ai — Hardware End Of Life Database when you require tools for databases.
Look up one hardware part number in the EOSL.ai database. Returns support status, End-of-Sale and End-of-Service-Life dates, support runway score, and the primary vendor bulletin URL backing the dates. Matching is exact, then punctuation-insensitive, then Fortinet short-SKU aliases (FG-60E -> FortiGate-60E). Returns found:false rather than guessing.
bulk_check
Check up to 200 part numbers in one call. Returns a per-part row (status, EOSL date, source URL, page URL) plus summary counts: past, endingSoon, supported, active, notFound.
search_models
Search tracked product families by vendor, product line, or series name (case-insensitive substring, e.g. "nexus 9300"). Returns up to 10 families with status, EOSL window, and page URL. Use get_family with a returned slug for the full record.
get_family
Fetch the full source-backed record for one product family by slug (from search_models or lookup_part pageUrl): lifecycle dates per SKU group, every part number, support runway score factors, and the vendor bulletin URLs.
list_vendors
List all vendors tracked by EOSL.ai with family counts and vendor page URLs.