Sealmark
Automated re-test on 2026-11-20: not checked by hand, and not yet reviewed by the maintainers.

Results / atilaahmettaner/tradingview-mcp

atilaahmettaner/tradingview-mcp

version tested 0.8.0GitHubtested 2026-11-20Sealmark 1.0.1methodology 0.3-draftSTANDARD run39 tools

Sealmark's automated test of atilaahmettaner/tradingview-mcp 0.8.0 on 2026-11-20 gave it grade D, its lowest test-area grade (protocol A and effects D). Tools reached with a valid call: 22 of 39. Of its 6 checks, 4 passed, 1 partial and 1 not applicable. 3 more checks are advisory, and advisory checks never change a grade: 1 passed and 2 not applicable. The run used Sealmark 1.0.1 with the standard settings.

D

Grade D

The server's grade is its lowest test-area grade. How grading works

Tools reached with a valid call: 22 of 39.

Grade by test area

A
Protocol4/4 points
D
Effects0.5/1 pointsincludes a weak signal, not a security finding

Protocol checks

CheckVerdictWhat happened
protocol
Valid MCP handshake and tool schemas
pass
handshake ok, 39 well-formed tool(s)
Evidence for protocol: 1 line
  1. Probe initialize + tools/list
    Outcome server TradingView Multi-Market Screener 1.30.0 answered; 39 tool(s)
    Decided from the MCP exchange (protocol)
tool-poisoningcritical
No tool-poisoning indicators in tool metadata
pass
scanned 39 tool definition(s), the server instructions and serverInfo, 1 resource(s), including parameter text: nothing suspicious
robust-input
Survives malformed tool input
pass
110 invalid call(s) rejected cleanly
Evidence for robust-input: 1 line
  1. Probe 110 invalid call(s) across 25 tool(s)
    Outcome all rejected cleanly and the server stayed responsive
    Decided from the MCP exchange (protocol)
secret-echocritical
No environment secret echoed in responses
pass
canary secrets absent from tools/list and 110 captured response(s), 0 of them successful result(s)
instructions-hygiene (advisory)
Server instructions name only tools that exist
pass
the instructions name no tool the server lacks
refusal-quality (advisory)
Refusals say what to do next
n/a
no refusal was recorded in this run, so there is nothing to judge

Effects checks

CheckVerdictWhat happened
annotation-honestyweak signal
Read-only tools change nothing
partial
declared read-only; only caches changed (sandbox home or temp): top_gainers
Weak signal, not a security finding. A tool declared read-only changed only cache files, in its sandbox home or temp folder. A partial counts as half a point.
openworld-honesty
Closed-world tools stay on the machine
n/a
no tool declares openWorldHint: false that could be given a harness-owned control argument
undeclared-writes (advisory)
Unannotated tools leave the sandbox unchanged
n/a
every tool carries annotations, nothing to check

Each check id links to what it tests and how to fix a failure. The same text is in sealmark explain <id>.

Under a check, Evidence shows what it probed (sent or inspected) and what it observed in this run: up to 6 lines per check, each cut at 240 characters, for checks that are not security checks. The text is shortened, and paths and anything that looks like a secret or token are replaced. Run sealmark run --format json yourself for every line in full.

By tool

Which checks called each tool with a valid call in this run, and which did not exercise it. A check can leave a tool out for several reasons: a limit Sealmark sets, a tool left out by design, input the run could not fill in, or a call that returned an error. The CLI report gives the reason. A verdict belongs to the whole check, not to one tool: a failed check that called three tools does not say which one failed. Security checks are left out of this table.

ToolCalled byNot exercised by
top_gainersNo check listed here called it with a valid call.None
top_losersNo check listed here called it with a valid call.None
bollinger_scanNo check listed here called it with a valid call.None
rating_filterNo check listed here called it with a valid call.None
coin_analysisNo check listed here called it with a valid call.None
consecutive_candles_scanNo check listed here called it with a valid call.None
advanced_candle_patternNo check listed here called it with a valid call.None
volume_breakout_scannerNo check listed here called it with a valid call.None
volume_confirmation_analysisNo check listed here called it with a valid call.None
smart_volume_scannerNo check listed here called it with a valid call.None
multi_agent_analysisNo check listed here called it with a valid call.None
egx_market_overviewNo check listed here called it with a valid call.None
egx_sector_scanNo check listed here called it with a valid call.None
egx_sector_scannerNo check listed here called it with a valid call.None
egx_index_analysisNo check listed here called it with a valid call.None
egx_stock_screenerNo check listed here called it with a valid call.None
egx_trade_planNo check listed here called it with a valid call.None
egx_fibonacci_retracementNo check listed here called it with a valid call.None
smart_money_analysisNo check listed here called it with a valid call.None
egx_smart_money_scannerNo check listed here called it with a valid call.None
multi_timeframe_analysisNo check listed here called it with a valid call.None
market_sentimentNo check listed here called it with a valid call.None
financial_newsNo check listed here called it with a valid call.None
combined_analysisNo check listed here called it with a valid call.None
backtest_strategyNo check listed here called it with a valid call.None
compare_strategiesNo check listed here called it with a valid call.
walk_forward_backtest_strategyNo check listed here called it with a valid call.
yahoo_priceNo check listed here called it with a valid call.
market_snapshotNo check listed here called it with a valid call.
bitcoin_market_pulseNo check listed here called it with a valid call.
stock_extended_hoursNo check listed here called it with a valid call.
stock_options_chainNo check listed here called it with a valid call.
stock_options_unusual_activityNo check listed here called it with a valid call.
futures_market_overviewNo check listed here called it with a valid call.
futures_top_moversNo check listed here called it with a valid call.
futures_category_snapshotNo check listed here called it with a valid call.
futures_watchlistNo check listed here called it with a valid call.
stock_screenerNo check listed here called it with a valid call.
stock_pricesNo check listed here called it with a valid call.

What was not covered

Grade over time

Since the run on

Same as that run: the same grade in every test area, the same server version (0.8.0), the same Sealmark version (1.0.1).

  1. Dv0.8.0Sealmark 1.0.0
  2. Dv0.8.0Sealmark 1.0.1
  3. Dv0.8.0Sealmark 1.0.1

Badge for the README

The badge shows this automated result for version 0.8.0. It is a link to this page, not a certificate, and it changes when the next re-test does.

Sealmark badge for atilaahmettaner/tradingview-mcp
The flat badge, one letter per graded test area.
[![Sealmark](https://sealmark.dev/badge/atilaahmettaner-tradingview-mcp.svg)](https://sealmark.dev/results/atilaahmettaner-tradingview-mcp/)

Files: badge SVG, card SVG, shields endpoint JSON.

Project facts

License
MIT
Repository
atilaahmettaner/tradingview-mcp
Last push
20 Nov 2026
Open issues and pull requests
7

From GitHub, checked 22 Nov 2026. Plain facts about the project; they play no part in the grade.

Run it yourself

This repeats the run with the same Sealmark version and the standard settings, starting the server the same way:

npx -y sealmark@1.0.1 run --start "uvx --from git+https://github.com/atilaahmettaner/tradingview-mcp tradingview-mcp"

To confirm your run used the standard settings, add --format json --out report.json to the command. In the report, config.standard should be true and config.hash should start with sha256:d13e7893a0ac, as they did in this run. If either differs, so did the settings, and the verdicts may too (STANDARD and CUSTOM runs).

To keep the setup, put the start command in sealmark.yaml as the server.

Grade alerts

One email when the grade of atilaahmettaner/tradingview-mcp changes after a re-test. Nothing else, and every email has a link to stop them.

Or follow it in a feed reader: the Atom feed lists each move of the overall grade that came with a different version of this server, tested with the same Sealmark version as the graded run before.

Each of 613 verdicts was checked independently, and Sealmark was wrong on some: how reliable Sealmark is.

Is this wrong?

Reply on the GitHub issue or email disclosure@sealmark.dev and we will recheck it. Maintainers can ask for their server to be removed.

If we were wrong, we correct the page and add your reply. Security findings go to the maintainer privately first; see the disclosure policy.