← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionOKX Agent Trade KitConnect AI assistants to OKX trading and account operations through MCP.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS51 / 100 · D75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions8 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation13 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • OKX users who want access through an AI client
  • Developers who need a local trading MCP server
  • Users who need combined market, trading, account, and earn capabilities
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users who do not use OKX
  • Users seeking only static documentation or offline data
  • Users unwilling to expose trading or account API permissions to an AI client
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • OKX API credentials are required for authenticated features
  • Some market functionality is available without authentication
  • The --read-only flag can restrict the server to query tools
  • Modules must be selected with --modules
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • Enabled trading or earn modules allow an AI client to initiate real operations
  • The permissions assigned to the API credentials affect account and trading access
  • Trading, bot, and earn operations can involve financial loss and market risk
  • OKX Outcomes requires a separate okx-outcomes binary and includes dry-run-gated trading functionality
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude Desktop, Cursor, Claude Code, VS Code, WindsurfClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011