{"id":"cdatasoftware-cdata-jdbc-mcp-server","name":"cdata-jdbc-mcp-server","af_score":45.5,"security_score":27.0,"reliability_score":27.5,"what_it_does":"Provides a generic MCP (Model Context Protocol) server that uses CData JDBC drivers to expose external data sources as SQL-like tables/columns and lets MCP clients run queries (and, despite the repo name/readme emphasis, it claims CRUD tools are available via MCP tools). Communication with the MCP client is via stdio on the same machine.","best_when":"When you run the MCP server locally alongside an MCP-capable desktop client (e.g., Claude Desktop) and you want agent-accessible, near-real-time data retrieval across many JDBC-supported sources.","avoid_when":"Avoid when you need a hosted/public API endpoint, cross-machine access, strong auth/rbac for the MCP server itself, or documented query-safety controls (since the tool exposes SQL execution).","last_evaluated":"2026-04-04T19:41:25.592737+00:00","has_mcp":true,"has_api":false,"auth_methods":["CData JDBC driver licensing (java -jar <driver>.jar --license)","Data-source authentication via the JDBC driver (e.g., OAuth in browser when required) as part of the JDBC connection string/JdbcUrl used in the .prp file"],"has_free_tier":false,"known_gotchas":["Server uses stdio, so it can only be used by clients running on the same machine.","The README claims read-only repo name but also states the AI client can use built-in tools to read/write/update/delete; tool exposure may not match “read-only” expectations—agents should be conservative.","SQL execution tool ({servername}_run_query) can be powerful; the README does not document safeguards, query parameterization, or restrictions against expensive/unsafe queries.","Metadata/tools output is returned as CSV; agents may need to parse CSV and handle quoting/encoding."],"error_quality":0.0}