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.

Dimensionmcp-knowledge-graphPersistent memory for AI models through a local knowledge graph.MCP ClickHouseConnect ClickHouse to your AI assistantsChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS56 / 100 · C79 / 100 · B75 / 100 · B
Reliability7 / 2012 / 2012 / 20
Security and permissions11 / 2018 / 2016 / 20
Maintenance8 / 2017 / 2014 / 20
Documentation16 / 2017 / 2018 / 20
Setup experience14 / 2015 / 2015 / 20
Best for
  • Claude users who need persistent memory across conversations
  • Developers who want local persistent memory in their projects
  • Users concerned about data privacy and prefer local storage over cloud
  • 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
  • Scenarios requiring distributed or high-concurrency storage
  • Advanced security needs like built-in encryption or access control
  • Users who wish to store memory files in the cloud managed by a service provider
  • 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
  • Read and write to the local file system (within specified --memory-path or project .aim directory)
  • Run npx commands to start the server
  • 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
  • Local files might be accidentally deleted or overwritten (the system has _aim marker protection, but risk remains)
  • Sensitive information stored locally could be exposed if not encrypted
  • Dependency on Node.js version and npm package management may cause conflicts
  • 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, Claude CodeClaude DesktopClaude Desktop
Tools10427