← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionGreptimeDB MCP ServerQuery and analyze GreptimeDB metrics, logs, and traces via SQL, TQL, and RANGE queries.ChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS60 / 100 · C75 / 100 · B
Reliability10 / 2012 / 20
Security and permissions12 / 2016 / 20
Maintenance11 / 2014 / 20
Documentation14 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers working with time-series and observability data.
  • Teams needing natural language access to their database for query and analysis.
  • Users wanting to integrate AI-assisted data exploration within MCP clients.
  • Drug discovery and computational chemistry researchers
  • Bioinformatics teams needing ChEMBL data through AI assistants
  • Developers comfortable with Node.js or Docker
Not for
  • Users who need write operations or DDL/DML (read-only by default; write mode only for local/test, extremely risky).
  • Users not using GreptimeDB.
  • Users who need direct database access without MCP integration.
  • 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 access to GreptimeDB for SQL, TQL, and RANGE queries.
  • Access to HTTP API (default port 4000) for pipeline and dashboard management.
  • Access to configured credentials via environment variables or CLI arguments.
  • Data masking is enabled by default to prevent sensitive column exposure.
  • 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
  • If write mode is enabled (disabled by default), AI could execute destructive SQL; never enable against production.
  • Queries may be expensive if complex or misused; restrict access and resources.
  • Providing secret environment variables over HTTP could increase exposure risk.
  • Database may be inaccessible due to network configuration or startup issues.
  • 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 DesktopClaude Desktop
Tools1327