M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionTeradata MCP ServerConnect AI agents directly to Teradata with enterprise security and extensibility.MCP ClickHouseConnect ClickHouse to your AI assistantsChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS47 / 100 · D79 / 100 · B75 / 100 · B
Reliability8 / 2012 / 2012 / 20
Security and permissions10 / 2018 / 2016 / 20
Maintenance8 / 2017 / 2014 / 20
Documentation9 / 2017 / 2018 / 20
Setup experience12 / 2015 / 2015 / 20
Best for
  • Developers building AI agents that need direct Teradata access
  • Users wanting to quickly create semantic layers
  • Users needing database admin capabilities
  • Users wanting to use RAG pipelines
  • Teams already using ClickHouse who want AI assistants to access data directly.
  • Scenarios requiring fast, read-only data queries and schema exploration.
  • Drug discovery and computational chemistry researchers
  • Bioinformatics teams needing ChEMBL data through AI assistants
  • Developers comfortable with Node.js or Docker
Not for
  • Non-Teradata database users
  • Users needing a full GUI management interface
  • Enterprises requiring official support (community project)
  • Scenarios requiring write access to the database without explicit opt-in.
  • Production environments with stringent security requirements that avoid default permission settings.
  • Production settings requiring official ChEMBL support (this is unofficial)
  • Users without a Node.js or Docker environment
  • General database tasks unrelated to ChEMBL
Required permissions
  • Requires Teradata database credentials
  • May need access to database objects (tables, views, stored procedures)
  • May execute SQL queries
  • May require file system access (depending on tool)
  • Requires read-only access to ClickHouse database (default).
  • Optional: write access via CLICKHOUSE_ALLOW_WRITE_ACCESS.
  • Optional: destructive operations via CLICKHOUSE_ALLOW_DROP.
  • Outbound network access to https://www.ebi.ac.uk/chembl/api/data
  • Read-only access to public API data; no authentication credentials required
Risks and side effects
  • Database credentials are stored in plaintext in environment
  • Executing SQL queries may modify data or impact performance
  • Row limit protection reduces token overflow risk
  • Community project, security should be self-assessed
  • If write access is enabled, AI might make unintended modifications.
  • If DROP access is enabled, data deletion could occur accidentally.
  • Credentials may be exposed via environment variables.
  • Unofficial project with license marked NOASSERTION (README claims MIT); verify licensing yourself
  • Data accuracy depends on the ChEMBL REST API and the server's parsing may contain defects
  • 30-second request timeouts may constrain large batch queries
  • README inconsistency on tool count (22 vs 27) raises documentation reliability concerns
Supported clientsClaude Desktop, VS Code, Open WebUI, FlowiseClaude DesktopClaude Desktop
Tools9427