← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionTwelve Data MCP ServerConnect AI assistants to Twelve Data financial market dataBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS52 / 100 · D75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions13 / 2016 / 20
Maintenance7 / 2018 / 20
Documentation11 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Individuals or teams with a Twelve Data account who want market data inside their AI assistant
  • Users who want a no-install setup via the hosted cloud connector
  • Developers who prefer to self-host with their own API key
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users without a Twelve Data account who don't want to sign up or authorize access
  • Fully offline scenarios with no third-party data dependency
  • General tasks unrelated to financial market data
  • 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
  • Cloud option: browser-based OAuth login linking your account to the Twelve Data hosted service
  • Local option: reads TWELVE_DATA_API_KEY from a .env file and uses it to call the Twelve Data API
  • Makes outbound network requests to fetch market data (to mcp.twelvedata.com for the cloud option, or directly to the Twelve Data API locally)
  • 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
  • The cloud server is hosted by Twelve Data, requiring account authorization to a third-party service
  • In local mode, the API key is stored in plaintext in the .env file and must be kept secure
  • Data access and rate limits are bound by your Twelve Data subscription plan
  • The repository does not specify an open-source license, leaving usage and redistribution terms unclear
  • 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, ChatGPTClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011