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.

DimensionSLayerAn embeddable, expressive semantic layer for AI agents and humansChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS48 / 100 · D75 / 100 · B
Reliability7 / 2012 / 20
Security and permissions9 / 2016 / 20
Maintenance10 / 2014 / 20
Documentation10 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Data teams wanting a governed data access surface for AI agents
  • Developers building analytical MCP servers or APIs on top of a warehouse
  • Teams with existing dbt, Cube, or Ossie semantic configs they want to reuse
  • Engineers embedding a semantic layer into Python apps
  • 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 write access to the database (SLayer connections are read-only)
  • Simple cases where direct SQL is sufficient and no semantic layer is needed
  • Non-Python stacks that cannot run the CLI or an MCP subprocess
  • 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-only database access to configured datasources
  • Environment variables holding database credentials such as DB_PASSWORD
  • Permission to run the local CLI and the MCP subprocess
  • Permission to modify Claude Code MCP configuration
  • 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 passed to the MCP subprocess via environment variables, so a compromised launching shell could expose them
  • Connections are read-only but can still read sensitive business data, so row-level security should be applied
  • Once connected via MCP, agents can run queries, so verify their query scope matches expectations
  • As a third-party project, availability and behavior depend on upstream maintenance
  • 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 CodeClaude Desktop
Tools027