{"id":"cdatasoftware-microsoft-exchange-mcp-server-by-cdata","name":"microsoft-exchange-mcp-server-by-cdata","af_score":40.8,"security_score":38.2,"reliability_score":27.5,"what_it_does":"Provides a locally hosted, read-only MCP server that wraps the CData JDBC Driver for Microsoft Exchange. It exposes Exchange data as relational SQL tables via MCP tools (get_tables, get_columns, run_query) using stdio for client communication (e.g., Claude Desktop).","best_when":"You want an on-machine MCP integration for Exchange data exploration and read-only querying using existing CData JDBC connectivity/authentication.","avoid_when":"You require strong operational controls for large/long-running queries (no rate-limit/pagination guidance shown) or you need audited, structured error handling beyond what the underlying driver/tool returns.","last_evaluated":"2026-04-04T19:34:36.783915+00:00","has_mcp":true,"has_api":false,"auth_methods":["CData JDBC Driver authentication mechanisms (e.g., OAuth if required by the JDBC driver; configured via JdbcUrl / connection string)","Local license activation for the CData JDBC driver (java -jar cdata.jdbc.exchange.jar --license)"],"has_free_tier":false,"known_gotchas":["Server runs over stdio, so it must be co-located with the MCP client process (not usable as a remote MCP service as described).","README claims tools for read-only access, but it also generically says 'read, write, update, and delete'—agents should rely on the explicit project description (read-only) to avoid unsafe assumptions.","No rate-limit, timeout, or result-size guidance is provided; agents may need to constrain queries to avoid excessive payloads."],"error_quality":0.0}