M
MCP Directory CURATED DIRECTORY
863 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.

DimensionMemory VaultSelf-hosted AI memory database with hybrid search, MCP tools, and a 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
Reliability9 / 2012 / 2012 / 20
Security and permissions12 / 2018 / 2016 / 20
Maintenance11 / 2017 / 2014 / 20
Documentation14 / 2017 / 2018 / 20
Setup experience10 / 2015 / 2015 / 20
Best for
  • Individual developers who want memory data fully self-hosted and never sent to the cloud
  • Users already comfortable operating PostgreSQL
  • People who want cross-session memory in Claude Desktop or Claude Code
  • Builders layering memory under their own AI tooling without maintaining a separate vector database (single instance)
  • 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
  • Organizations needing multi-user or multi-tenant team collaboration (v1.0 is single-instance; team features are planned PRO)
  • Users who want a zero-ops hosted service
  • Projects requiring multilingual entity extraction (NER is English-only)
  • Anyone unwilling to run and maintain PostgreSQL
  • Deployments expecting transport encryption to come from the server itself (you must add a reverse proxy or tunnel)
  • 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/write access to the PostgreSQL database (DB_USER needs read/write on the memory vault database)
  • The database password (DB_PASSWORD is a secret value)
  • In stdio mode, a local process that reads environment variables and connects to the database
  • When HTTP/SSE is enabled, a listening port plus bearer token validation on every request
  • The dashboard stores its bearer token in browser localStorage
  • 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
  • With stdio, database credentials sit in plaintext in the client config's env block
  • The HTTP/SSE transport has no transport encryption of its own; tokens travel in a header, so put TLS in front of it
  • Publishing the container port on 0.0.0.0 reaches the whole network
  • API_AUTH_ENABLED=false only opens the REST API (the MCP transport still returns 401) and is a local-development convenience only
  • Known knowledge-graph limits: no fuzzy entity matching (PostgreSQL and Postgres stay separate), no re-extraction on edit, and one name can appear as both a Person and a Project entity
  • Single-maintainer project — reviews and responses depend on the maintainer's available time
  • 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
Tools6427