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.

DimensionTradingView MCP BridgeAI-assisted TradingView chart analysis and Pine Script development via Chrome DevTools ProtocolBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS53 / 100 · D75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions11 / 2016 / 20
Maintenance9 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience11 / 2014 / 20
Best for
  • Individual traders/researchers with a paid TradingView subscription who run TradingView Desktop
  • Developers who want AI assistance writing and debugging Pine Script
  • Researchers studying human-AI collaboration on professional financial interfaces
  • Claude Code users who want chart automation on their own machine
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Use cases requiring TradingView's official APIs or cloud services
  • Automated trading bots or algorithmic order execution
  • Commercial redistribution or resale of TradingView market data
  • Users without a paid TradingView subscription or the Desktop app installed
  • Production environments needing a stable, officially supported API rather than an undocumented interface that can break on updates
  • 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
  • Requires TradingView Desktop to be explicitly launched with `--remote-debugging-port=9222`, opening a local debug port
  • Requires Node.js 18+ and local filesystem access to clone and run the MCP server
  • Requires an active, logged-in TradingView subscription
  • The MCP server itself communicates with Claude Code over stdio and is not exposed to the network
  • 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
  • Relies on undocumented internal TradingView Electron/CDP interfaces that can change or break without notice on updates
  • Opening the local debug port means other processes on the same machine could theoretically access it
  • Automated reading/processing of TradingView data may conflict with TradingView's Terms of Use restrictions on automated data collection — usage compliance is the user's responsibility
  • Not affiliated with or supported by TradingView Inc., so long-term compatibility is not guaranteed
  • The README explicitly warns against redistributing data or circumventing paywalls; misuse could risk account suspension
  • 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 CodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools6211