Tradingview MCP

TradingView MCP server — real-time market data, technical analysis, screeners & backtesting for Claude, ChatGPT, Cursor & any MCP client. Stocks, crypto, forex & futures across global exchanges. Hosted or self-host.

MCP Servers Python Listed MIT

Is Tradingview MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.3 / 10
Provenance None
Signed commits 55%
Last push 25d ago
Compare Tradingview MCP
Suggest a correction

In detail: Tradingview MCP scores 54.5/100 (Grade C), ranked #801 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.3/10; 55% of recent commits are signed; last pushed 2026-09-01. Every point is earned from checkable signals — never paid placement. How scoring works →

How Tradingview MCP compares in MCP Servers

  1. #444 Ris MCP Ts 54.6 +0.1
  2. #445 Reddit Research MCP 54.5 ±0
  3. #446 Tradingview MCP 54.5 this agent
  4. #447 Mistral MCP 54.5 ±0
  5. #448 OrangePro 54.5 ±0

Bars show each HVTrust score; the tick marks Tradingview MCP’s 54.5.

Where the 54.5 comes from

HVTrust dimensions vs the MCP Servers average

54.5 / 100 · 100.0% confidence

Tradingview MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.1 / 25
2.2 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
13.9 / 20
1.8 above avg 12.1
AdoptionLog-scaled stars · package downloads
8.8 / 20
1.6 above avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-26
Rank Moved
Rank dropped 18 spots (#783 → #801)
2026-09-25
Rank Moved
Rank dropped 38 spots (#745 → #783)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.3/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
68.9
Activity sub-score · out of 100
#446

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 25 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
4.6k
Forks
962
Last Push
2026-09-01
25 days ago
Commits (4 wk)
7
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
7
Rank Change
▼18
was #783

Analysis

Activity Inputs

68.9 / 100
StarsRepository reach
22.0 / 30
FreshnessLast push recency
21.5 / 25
ActivityRecent commits
11.3 / 25
CommunityFork signal
13.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.3 / 10
OpenSSF Scorecard · scanned Sep 23, 2026
Signed Commits
55%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 1
Contributors 6
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Common questions about Tradingview MCP

Public trust evidence for Tradingview MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Tradingview MCP publish package provenance?
No published build provenance is currently detected for Tradingview MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Tradingview MCP have an OpenSSF Scorecard?
Tradingview MCP has an OpenSSF Scorecard score of 4.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Tradingview MCP actively maintained?
Maintained. Last push was 25 days ago.
What license does Tradingview MCP use?
Tradingview MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Tradingview MCP's commits signed?
55% of the last 100 commits to Tradingview MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Tradingview MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Tradingview MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Tradingview MCP?

For maintainers

HVTrust scores Tradingview MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 23Listed 2HVTrust 2Grade 2Score 1Scorecard 1Delisted 1MCP 1Surface 1
2026-09-26
Rank Moved
Rank dropped 18 spots (#783 → #801)
2026-09-25
Rank Moved
Rank dropped 38 spots (#745 → #783)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 296 spots (#442 → #738)
2026-09-23
HVTrust Changed
HVTrust up 11.8pts (44.5 → 56.3)
2026-09-22
Newly Listed
First tracked at rank #442
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-08
Rank Moved
Rank dropped 13 spots (#664 → #677)
2026-09-07
Rank Moved
Rank dropped 45 spots (#619 → #664)
2026-09-06
Rank Moved
Rank dropped 11 spots (#608 → #619)
2026-09-05
Rank Moved
Rank dropped 80 spots (#528 → #608)
2026-09-04
Rank Moved
Rank dropped 26 spots (#502 → #528)
2026-09-03
Scorecard Added
OSSF Scorecard: 4.3/10
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank rose 710 spots (#1212 → #502)
2026-09-03
HVTrust Changed
HVTrust up 33.1pts (24.8 → 57.9)
2026-09-02
Rank Moved
Rank dropped 33 spots (#1179 → #1212)
2026-09-01
Activity Score Changed
Activity score up 7pts (72 → 78)
2026-08-31
Rank Moved
Rank dropped 30 spots (#1147 → #1177)
2026-08-30
Rank Moved
Rank dropped 38 spots (#1109 → #1147)
2026-08-29
Rank Moved
Rank dropped 40 spots (#1069 → #1109)
2026-08-28
Rank Moved
Rank dropped 80 spots (#989 → #1069)
2026-08-27
Rank Moved
Rank dropped 24 spots (#965 → #989)
2026-08-26
Rank Moved
Rank dropped 103 spots (#862 → #965)
2026-08-24
Rank Moved
Rank rose 25 spots (#885 → #860)
2026-08-19
Rank Moved
Rank dropped 12 spots (#870 → #882)
2026-08-17
Rank Moved
Rank rose 12 spots (#882 → #870)
2026-08-16
Rank Moved
Rank dropped 28 spots (#854 → #882)
2026-08-14
Rank Moved
Rank dropped 10 spots (#841 → #851)
2026-08-12
Rank Moved
Rank dropped 15 spots (#819 → #834)
2026-08-10
Rank Moved
Rank dropped 45 spots (#772 → #817)
2026-08-08
Newly Listed
First tracked at rank #787

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.5 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/tradingview-mcp.svg)](https://hvtracker.net/agents/tradingview-mcp)
HTML:
<a href="https://hvtracker.net/agents/tradingview-mcp"><img src="https://hvtracker.net/badge/tradingview-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON