Tradingview MCP

TradingView MCP server — real-time market data, technical analysis, screeners & backtesting for Claude, ChatGPT, Cursor

MCP Servers Python Grade C Listed MIT
57.8/100
Rank #510 of 1320
Compare Tradingview MCP

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-01 · 3d ago
Recent change
Scorecard +9

Is Tradingview MCP safe? Tradingview MCP scores 57.8/100 (Grade C), ranked #510 of 1320 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 →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
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.
77.5
Activity sub-score · out of 100
#233

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-04 14:03 UTC · Repo last pushed 3 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
4.4k
Forks
922
Last Push
2026-09-01
3 days ago
Commits (4 wk)
23
Downloads (7d)
HN mentions (30d)
Open Issues
6
Rank Change
▼8
was #502

Analysis

HVTrust Dimensions vs MCP Servers

57.8 / 100 · 100.0% confidence

Tradingview MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.1 / 25
1.4 below avg 9.5
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 11.8
Maintenance60% last-push freshness · 40% commit activity
17.3 / 20
5.1 above avg 12.2
AdoptionLog-scaled stars · package downloads
8.7 / 20
2.5 above avg 6.2

Activity Inputs

77.5 / 100
StarsRepository reach
21.8 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
17.2 / 25
CommunityFork signal
13.8 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.3 / 10
OpenSSF Scorecard · scanned Sep 4, 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

Is Tradingview MCP safe?

Tradingview MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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?
Actively maintained. The repository was pushed to within the last 3 day(s).
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

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 15Listed 1Score 1HVTrust 1Grade 1Scorecard 1
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 57.8 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