Tradingview Indicator Search MCP Server

Findings (18)

• highHigh. Something risky that needs a close look before you install.
  dependencies issue

  Details are available to the maintainer after claiming this listing.
• highHigh. Something risky that needs a close look before you install.
  dependencies issue

  Details are available to the maintainer after claiming this listing.
• highHigh. Something risky that needs a close look before you install.
  dependencies issue

  Details are available to the maintainer after claiming this listing.
• mediumMedium. Worth checking, often a vulnerable dependency or a setup problem.
  @modelcontextprotocol/sdk@1.29.0: 6 known vulnerabilities

  GHSA-22jm-h49p-29qw, GHSA-46jr-4wx8-v453, GHSA-6prh-2h8m-c8cw, GHSA-6qxp-vccf-f47h, GHSA-f897-62hf-6gxq +1 more

  package-lock.json
• mediumMedium. Worth checking, often a vulnerable dependency or a setup problem.
  body-parser@2.3.0: 1 known vulnerability

  GHSA-27r3-jxmh-p828

  package-lock.json
• mediumMedium. Worth checking, often a vulnerable dependency or a setup problem.
  fast-uri@3.1.4: 11 known vulnerabilities

  GHSA-333x-w4r6-6crp, GHSA-5jgf-p345-68v8, GHSA-7p8r-x3mc-p8w7, GHSA-f65p-4m7j-42xc, GHSA-fph4-wmhf-6fwf +6 more

  package-lock.json
• mediumMedium. Worth checking, often a vulnerable dependency or a setup problem.
  nanoid@3.3.16: 1 known vulnerability

  GHSA-2v37-7h3g-55p8

  package-lock.json
• mediumMedium. Worth checking, often a vulnerable dependency or a setup problem.
  source-map-js@1.2.1: 1 known vulnerability

  GHSA-68fv-2mgg-jv7q

  package-lock.json
• mediumMedium. Worth checking, often a vulnerable dependency or a setup problem.
  vite@5.4.21: 8 known vulnerabilities

  GHSA-4w7w-66w2-5vf9, GHSA-587h-7wmj-h5pm, GHSA-698v-4r3x-3vcv, GHSA-9jrq-w75r-8gcw, GHSA-fx2h-pf6j-xcff +3 more

  package-lock.json
• mediumMedium. Worth checking, often a vulnerable dependency or a setup problem.
  zod@4.4.3: 1 known vulnerability

  GHSA-mrhx-c7xc-m3w5

  package-lock.json
• lowLow. Minor, or common in normal tools. Shown for information.
  @hono/node-server@1.19.15: 1 known vulnerability

  GHSA-rmxm-3fg6-px4f

  package-lock.json
• lowLow. Minor, or common in normal tools. Shown for information.
  @vitest/mocker@2.1.9: 2 known vulnerabilities

  GHSA-82fw-gwwq-j7x9, GHSA-qxg6-89mg-rqv8

  package-lock.json
• lowLow. Minor, or common in normal tools. Shown for information.
  esbuild@0.21.5: 1 known vulnerability

  GHSA-67mh-4wv8-2f99

  package-lock.json
• lowLow. Minor, or common in normal tools. Shown for information.
  hono@4.12.32: 9 known vulnerabilities

  GHSA-54fx-42gc-7vw4, GHSA-5r4p-p66f-jhc7, GHSA-79qm-7rj5-m7r9, GHSA-8j4g-w8fx-2239, GHSA-crvj-82cr-hjcx +4 more

  package-lock.json
• lowLow. Minor, or common in normal tools. Shown for information.
  ip-address@10.3.1: 5 known vulnerabilities

  GHSA-2vr4-cq9g-pvrc, GHSA-h3mg-xc3c-68pw, GHSA-j6r3-76f7-8jcv, GHSA-rpw4-54j3-4h4q, GHSA-rxp7-6hxx-x8q5

  package-lock.json
• lowLow. Minor, or common in normal tools. Shown for information.
  qs@6.15.3: 3 known vulnerabilities

  GHSA-4mjr-xmp4-gh2g, GHSA-6pq8-jhm2-2vcw, GHSA-x5fp-wj9c-mxmx

  package-lock.json
• lowLow. Minor, or common in normal tools. Shown for information.
  No manifest declaring network access and environment variables (agent.json)
• lowLow. Minor, or common in normal tools. Shown for information.
  Contacted these domains while starting up (no manifest to compare against)

  registry.npmjs.org

Network activity

Tools exposed (7)

• search_scripts

  Search TradingView for public indicators and strategies by topic, for example "trend following", "scalping", "order blocks", "mean reversion", "volume profile". Topic search is curated by TradingView and gives far better results than free-text keyword matching. Omit `query` to get the top/trending f

• list_editors_picks

  TradingView's editors' picks: the hand-curated, highest-quality community scripts. Best starting point when you want proven, well-built indicators rather than a broad sweep.

• list_author_scripts

  List every public script published by one TradingView author, for example "TraderlifestyleYT", "LuxAlgo", "ZenAndTheArtOfTrading". Use this when you have a favourite author and want their catalogue. Optionally narrow with `query`.

• get_script_source

  Fetch the full Pine Script source for one script, ready to backtest or port. Pass `script_id_part` from any search result (form "PUB;<hash>"), or paste a TradingView `chart_url` and it will be resolved. Sources are cached permanently per version, so repeat calls cost no request. Closed-source script

• harvest_scripts

  Bulk-collect many scripts AND their Pine sources into the local corpus in one go, for example "100 trend-following strategies". This is the efficient way to build a backtesting library: pay the network cost once here, then use query_corpus offline. Runs within a wall-clock budget and checkpoints as

• query_corpus

  Search everything already collected locally. Zero network requests, instant, and it can search INSIDE Pine source code, which the TradingView site cannot do. Use `source_contains` for literal code tokens such as "ta.supertrend" or "strategy.entry", and `query` for full-text over names, authors and d

• fetch_status

  Show rate-limit health and corpus size: requests used against the daily budget, whether the circuit breaker has tripped, current pacing settings, and how many scripts and sources are stored locally. Makes no network request.