← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionTradingView MCP ServerExpose TradingView market data, multi-exchange screeners, and a backtesting engine to AI assistantsBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS62 / 100 · C75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions14 / 2016 / 20
Maintenance11 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Traders and quant hobbyists researching market data inside AI assistants
  • Users of MCP clients such as Claude Desktop and Cursor
  • Developers who need a cacheable, fault-tolerant market data pipeline
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users seeking real financial advice or guaranteed returns
  • Users needing live order execution or brokerage integration
  • Users expecting an officially certified TradingView server
  • 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
  • Access to public scanner.tradingview.com endpoints
  • Access to Yahoo Finance, Reddit JSON API, and RSS financial feeds
  • Optional Redis connection (REDIS_URL / host / port)
  • No TradingView account or API key required
  • 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
  • Backtests use historical data with simulated costs and do not predict future results
  • Relies on public endpoints subject to rate limits or upstream failures
  • Outputs are informational only, not financial advice
  • Not an official TradingView project
  • 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, CursorClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011