Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TradingMCP

REMOTE · MCP.CRYPTOSIEVE.COM · 2 COMPONENTS

Market analysis for AI assistants: screeners, multi-timeframe analysis, backtests, in-chat charts.

0 this week 80 Trust /100

Last scanned (13 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability47
  • 25% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 8684 tokens (~173/item across 50 items; 46 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage72
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 2% of tool parameters carry a description.Partial
  • Structured output schemas are declared (17% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 47 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Nov 26 0
    • Tool “smart_money_analysis” rewrote its description, which is the text the model reads security
    • Tool “yahoo_price” rewrote its description, which is the text the model reads security
  • 15 Nov 26 0
    • Tool “price_chart” rewrote its description, which is the text the model reads security
    • Tool “coin_analysis” rewrote its description, which is the text the model reads security
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.cryptosieve.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cryptosieve.com CN=WE1,O=Google Trust Services,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA256 84d9c79268da107613786390a0b827ee
SANs: cryptosieve.com, *.cryptosieve.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.cryptosieve.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
cryptosieve.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.cryptosieve.com/mcp Verified 200
http (plaintext) http://mcp.cryptosieve.com/mcp HTTPS enforced 308 https://mcp.cryptosieve.com/mcp
MCP tools · 46 exposed · ~8,652 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
advanced_candle_pattern ~143

Advanced candle pattern analysis using multi-timeframe data. Args: exchange: Exchange name (BINANCE, KUCOIN, etc.) base_timeframe: Base timeframe for analysis (5m, 15m, 1h, 4h) pattern_length: Number of consecutive periods to analyse (2-4) min_size_increase: Minimum percentage increase in candle size limit: Maximum number of results to return

NameTypeReqDescription
base_timeframestring––
exchangestring––
limitinteger––
min_size_increasenumber––
pattern_lengthinteger––

No output schema declared.

No examples provided.

backtest_chart ~158

Run a strategy backtest and render its equity curve as an interactive chart in the conversation (capital growth + drawdown, with return / win-rate / Sharpe stats). Strategies: rsi, bollinger, macd, ema_cross, supertrend, donchian, rsi_pullback, keltner_breakout, triple_ema. period: 1mo|3mo|6mo|1y|2y, interval: 1d|1h. Clients without interactive app support can read the `summary` field.

NameTypeReqDescription
initial_capitalnumber––
intervalstring––
periodstring––
strategystring––
symbolstringyes–

No output schema declared.

No examples provided.

backtest_strategy ~307

Backtest a trading strategy on historical data with institutional-grade metrics. Args: symbol: Yahoo Finance symbol (AAPL, BTC-USD, THYAO.IS, ^GSPC) strategy: rsi | bollinger | macd | ema_cross | supertrend | donchian | rsi_pullback | keltner_breakout | triple_ema (rsi_pullback and triple_ema need period >= '1y' for SMA200 warmup) period: '1mo', '3mo', '6mo', '1y', '2y' initial_capital: Starting capital in USD (default $10,000) commission_pct: Per-trade commission % (default 0.1%) slippage_pct: Per-trade slippage % (default 0.05%) interval: '1d' (daily) or '1h' (hourly) include_trade_log: Include full per-trade log (default False) include_equity_curve: Include equity curve data points (default False)

NameTypeReqDescription
commission_pctnumber––
include_equity_curveboolean––
include_trade_logboolean––
initial_capitalnumber––
intervalstring––
periodstring––
slippage_pctnumber––
strategystringyes–
symbolstringyes–

No output schema declared.

No examples provided.

bitcoin_market_pulse ~211

Single-call BTC macro context: price, dominance, total market cap + risk assessment. Use this WHENEVER analyzing any cryptocurrency (altcoin or BTC itself) to get the broader market frame in one shot. A SOL/ETH/whatever setup looks very different when BTC is dumping with rising dominance vs. when alts are leading. Calling this once gives Claude the macro context to provide Bitcoin-aware commentary alongside the per-coin analysis - without chaining 2-3 separate yahoo_price + manual reasoning calls. Returns: - bitcoin: price, 24h change %, volume, market cap - dominance: BTC and ETH market-cap share of total crypto - total_market: total crypto mcap + 24h change + active coin count - assessment: label (HIGH_RISK / ALT_RISK / ALT_FAVORABLE / OPPORTUNITY_WITH_CAUTION / NEUTRAL) + 1-paragraph reasoning

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bollinger_scan ~374

Scan for assets with low Bollinger Band Width (squeeze detection). Works with crypto and stocks. This scans a whole EXCHANGE for squeezes (canonical name is exactly `bollinger_scan`; there is no "get_bollinger_band_analysis" tool). For the Bollinger read of ONE symbol, call `coin_analysis` instead. Example: bollinger_scan(exchange="BINANCE", timeframe="15m", bbw_threshold=0.008) Args: exchange: Exchange — crypto: KUCOIN, BINANCE, BYBIT, MEXC; stocks: EGX, BIST, NASDAQ, NYSE, BURSA, HKEX, SSE, SZSE, TWSE, TPEX, EPA (Euronext Paris), AMS, BRU, LIS, MIL, LSE, SIX, BME, XETRA, FWB, TSX, TSXV, NSE, BSE (India), IDX (Indonesia) timeframe: One of 5m, 15m, 1h, 4h, 1D, 1W, 1M. Typical squeeze thresholds: 15m→0.008, 1h→0.02, 4h→0.04, 1D→0.12 bbw_threshold: Maximum BBW value to filter (default 0.04) limit: Number of rows to return (max 100) Returns ``list[dict]`` on success. On ANY failure returns a structured error envelope ``{"error": {"code": ..., "retryable": ...}}``.

NameTypeReqDescription
bbw_thresholdnumber––
exchangestring––
limitinteger––
timeframestring––
NameTypeReqDescription
result–yes–

No examples provided.

coin_analysis ~436

Get detailed analysis for a specific asset (coin or stock) on specified exchange and timeframe. This is the canonical single-symbol technical readout (there is no "get_technical_analysis" or "get_technical_summary" tool — use THIS one). Use `multi_timeframe_analysis` instead when you need trend alignment across several timeframes, and `combined_analysis` when you also want news sentiment + headlines in the same call. Futures contracts (ES1!, CL1!, …) and oil/gas/copper are quoted by the futures_* tools, not analysed here; gold, silver, platinum and palladium are (GC1! → TVC:GOLD). Example: coin_analysis(symbol="BTCUSDT", exchange="BINANCE", timeframe="1h") Args: symbol: Bare ticker, no exchange prefix — crypto: "BTCUSDT", "ETHUSDT"; stocks: "COMI" (EGX), "THYAO" (BIST), "600519" (SSE), "300251" (SZSE), "2330" (TWSE), "3105" (TPEX) exchange: Exchange — crypto: KUCOIN, BINANCE, MEXC; stocks: EGX, BIST, NASDAQ, NYSE, BURSA, HKEX, SSE, SZSE, TWSE, TPEX, EPA (Euronext Paris), AMS, BRU, LIS, MIL, LSE, SIX, BME, XETRA, FWB, TSX, TSXV, NSE, BSE (India), IDX (Indonesia). If the symbol isn't listed there, the error's `listed_on` field names exchanges that do list it. timeframe: Time interval (5m, 15m, 1h, 4h, 1D, 1W, 1M) Returns: Detailed analysis with all indicators and metrics

NameTypeReqDescription
exchangestring––
symbolstringyes–
timeframestring––

No output schema declared.

No examples provided.

combined_analysis ~213

POWER TOOL: TradingView technical analysis + news sentiment + financial news. Use this when you want TA AND sentiment AND news for one symbol in a single call. For indicators only, `coin_analysis` is faster; for cross-timeframe trend alignment use `multi_timeframe_analysis`. Example: combined_analysis(symbol="NVDA", exchange="NASDAQ", timeframe="1D") Args: symbol: Bare ticker, no exchange prefix ("AAPL", "BTCUSDT", "THYAO", "GDX") exchange: Exchange (NASDAQ, NYSE, AMEX, NYSEARCA, PCX, BINANCE, KUCOIN, MEXC, BIST, EGX, TWSE, TPEX) timeframe: Analysis timeframe (5m, 15m, 1h, 4h, 1D, 1W)

NameTypeReqDescription
exchangestring––
symbolstringyes–
timeframestring––

No output schema declared.

No examples provided.

compare_strategies ~197

Run all 9 strategies (RSI, Bollinger, MACD, EMA Cross, Supertrend, Donchian, RSI Pullback, Keltner Breakout, Triple EMA) and return a ranked leaderboard. Args: symbol: Yahoo Finance symbol (AAPL, BTC-USD, SPY…) period: '1mo', '3mo', '6mo', '1y', '2y' (period >= '1y' recommended so rsi_pullback and triple_ema can complete SMA200 warmup; otherwise they contribute zero trades) initial_capital: Starting capital in USD (default $10,000) interval: '1d' (daily) or '1h' (hourly)

NameTypeReqDescription
initial_capitalnumber––
intervalstring––
periodstring––
symbolstringyes–

No output schema declared.

No examples provided.

consecutive_candles_scan ~167

Scan for coins with consecutive growing/shrinking candles pattern. Args: exchange: Exchange name (BINANCE, KUCOIN, etc.) timeframe: Time interval (5m, 15m, 1h, 4h) pattern_type: "bullish" (growing candles) or "bearish" (shrinking candles) candle_count: Number of consecutive candles to check (2-5) min_growth: Minimum growth percentage for each candle limit: Maximum number of results to return

NameTypeReqDescription
candle_countinteger––
exchangestring––
limitinteger––
min_growthnumber––
pattern_typestring––
timeframestring––

No output schema declared.

No examples provided.

egx_fibonacci_retracement ~146

Fibonacci retracement analysis for EGX stocks. Args: symbol: EGX stock symbol (e.g., "COMI", "TMGH", "FWRY") lookback: Period for swing high/low — "1M", "3M", "6M", "52W", "ALL" (default 52W) timeframe: Analysis timeframe (5m, 15m, 1h, 4h, 1D, 1W, 1M — default 1D)

NameTypeReqDescription
lookbackstring––
symbolstringyes–
timeframestring––

No output schema declared.

No examples provided.

egx_index_analysis ~129

Analyse an EGX index showing constituent performance with full indicators. Args: index: EGX30, EGX70, EGX100, SHARIAH33, EGX35LV, TAMAYUZ timeframe: One of 5m, 15m, 1h, 4h, 1D, 1W, 1M (default 1D) limit: Number of stocks to show in detail (max 100)

NameTypeReqDescription
indexstring––
limitinteger––
timeframestring––

No output schema declared.

No examples provided.

egx_market_overview ~96

Get a comprehensive overview of the Egyptian Exchange (EGX) market. Args: timeframe: One of 5m, 15m, 1h, 4h, 1D, 1W, 1M (default 1D for stocks) limit: Number of stocks per category (max 20)

NameTypeReqDescription
limitinteger––
timeframestring––

No output schema declared.

No examples provided.

egx_sector_scan ~121

Scan EGX stocks by sector. Shows available sectors if none specified. Args: sector: Sector name (banks, healthcare_and_pharma, real_estate, etc.) Leave empty to list all sectors. timeframe: One of 5m, 15m, 1h, 4h, 1D, 1W, 1M limit: Max results per sector (max 50)

NameTypeReqDescription
limitinteger––
sectorstring––
timeframestring––

No output schema declared.

No examples provided.

egx_sector_scanner ~170

Sector rotation scanner for EGX — identifies hot/cold sectors and top picks. Args: timeframe: One of 5m, 15m, 1h, 4h, 1D, 1W, 1M (default 1D) top_n_sectors: Number of top sectors to show stock picks for (1-18, default 5) top_n_stocks: Number of top stocks per highlighted sector (1-10, default 3) min_stock_score: Minimum stock score for picks (0-100, default 60)

NameTypeReqDescription
min_stock_scoreinteger––
timeframestring––
top_n_sectorsinteger––
top_n_stocksinteger––

No output schema declared.

No examples provided.

egx_smart_money_scanner ~214

Rank EGX index constituents by smart-money accumulation evidence. Runs the full smart_money_analysis per constituent (Yahoo .CA history, bounded thread pool) and ranks by the volume-flow composite score, with the banker decomposition and oscillator state attached per row. Rows the data source can't serve are listed under `skipped`, never silently dropped. Args: index: EGX30 | EGX70 | EGX100 | SHARIAH33 | EGX35LV | TAMAYUZ limit: Max ranked rows to return (default 10, max 50) period: History window — 1mo | 3mo | 6mo | 1y | 2y (default 6mo) min_score: Only include rows with composite score >= this (0-100)

NameTypeReqDescription
indexstring––
limitinteger––
min_scorenumber––
periodstring––

No output schema declared.

No examples provided.

egx_stock_screener ~162

Production stock ranking engine for EGX — finds strong stocks with actionable setups. Args: timeframe: One of 5m, 15m, 1h, 4h, 1D, 1W, 1M (default 1D) min_score: Minimum stock score to include (0-100, default 55) index_filter: Filter by index — EGX30, EGX70, EGX100, SHARIAH33, EGX35LV, TAMAYUZ limit: Number of results (max 50)

NameTypeReqDescription
index_filterstring––
limitinteger––
min_scoreinteger––
timeframestring––

No output schema declared.

No examples provided.

egx_trade_plan ~102

Generate a full trade plan for a specific EGX stock. Args: symbol: EGX stock symbol (e.g., "COMI", "TMGH", "FWRY") timeframe: One of 5m, 15m, 1h, 4h, 1D, 1W, 1M (default 1D)

NameTypeReqDescription
symbolstringyes–
timeframestring––

No output schema declared.

No examples provided.

financial_news ~82

Real-time financial news via Marketaux (licensed). Args: symbol: Optional symbol filter ("AAPL", "BTC"). None = all news. category: News category ("crypto", "stocks", "all") limit: Max number of news items

NameTypeReqDescription
categorystring––
limitinteger––
symbol–––

No output schema declared.

No examples provided.

futures_category_snapshot ~106

Quote all major front-month contracts in a specific futures category. Args: category: equity_index | energy | metals | agriculture | rates | forex | crypto_futures Returns: OHLCV quotes for the standard watchlist of contracts in that category. Example symbols: ES1! NQ1! (equity_index), CL1! NG1! (energy), GC1! SI1! (metals).

NameTypeReqDescription
categorystring––

No output schema declared.

No examples provided.

futures_market_overview ~150

Top futures contracts sorted by trading volume. Args: category: all | equity_index | energy | metals | agriculture | rates | forex | crypto_futures exchanges: us (CME, COMEX, NYMEX, CBOT) | global (adds ICE, EUREX) limit: max contracts to return (default 30) volume_min: minimum volume filter (0 = no filter) Returns: Dict with total_available count and list of contracts with OHLCV + % change.

NameTypeReqDescription
categorystring––
exchangesstring––
limitinteger––
volume_mininteger––

No output schema declared.

No examples provided.

futures_top_movers ~110

Futures contracts with the biggest percentage moves today. Args: direction: gainers | losers exchanges: us | global limit: max results volume_min: minimum volume filter (default 10, filters illiquid contracts) Returns: List of futures ranked by % change with OHLCV data.

NameTypeReqDescription
directionstring––
exchangesstring––
limitinteger––
volume_mininteger––

No output schema declared.

No examples provided.

futures_watchlist ~58

Return the full categorized list of well-known front-month futures symbols. Categories: equity_index, energy, metals, agriculture, rates, forex, crypto_futures. Use these symbols with futures_category_snapshot or coin_analysis for deeper analysis.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

market_sentiment ~90

News sentiment for stocks and crypto (licensed Marketaux entity sentiment). Args: symbol: Asset symbol ("AAPL", "BTC", "ETH", "TSLA") category: News group to search ("crypto", "stocks", "all") limit: Max articles to analyse

NameTypeReqDescription
categorystring––
limitinteger––
symbolstringyes–

No output schema declared.

No examples provided.

market_snapshot ~32

Global market overview: major indices, top crypto, FX rates, and key ETFs. Powered by Yahoo Finance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

markets_dashboard ~200

The user's live market board. Start here when they ask how the markets are doing in general: "how are the markets today?", "what's moving?", "market update", a morning check before the open, or "open the market dashboard". One call covers the overview: the user's own symbols on top (their watchlist, then what they asked about most in the last 30 days), then major indices (US, India, Türkiye, Indonesia, VIX), crypto, commodities and FX, each with today's change. Don't also call market_snapshot for the same overview; add other tools only for what the board doesn't show (futures, news, sectors). For a single symbol's price or analysis, use that symbol's own tool instead. Opens as an interactive dashboard; clicking a row asks for that market's chart or analysis. Clients without app support can read the `summary` field.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

multi_agent_analysis ~273

Run a multi-agent debate (Technical, Sentiment, Risk) for a specific symbol. Args: symbol: Symbol — crypto: "BTCUSDT"; stocks: "COMI" (EGX), "THYAO" (BIST), "600519" (SSE), "300251" (SZSE), "2330" (TWSE), "3105" (TPEX), "GDX" (AMEX) exchange: Exchange — crypto: KUCOIN, BINANCE, MEXC; stocks: EGX, BIST, NASDAQ, NYSE, AMEX, NYSEARCA, PCX, SSE, SZSE, TWSE, TPEX, EPA (Euronext Paris), AMS, BRU, LIS, MIL, LSE, SIX, BME, XETRA, FWB, TSX, TSXV, NSE, BSE (India), IDX (Indonesia) timeframe: Time interval (5m, 15m, 1h, 4h, 1D, 1W) Returns: A structured debate between 3 AI agents culminating in a final trading decision.

NameTypeReqDescription
exchangestring––
symbolstringyes–
timeframestring––

No output schema declared.

No examples provided.

multi_timeframe_analysis ~312

Multi-timeframe alignment analysis (Weekly → Daily → 4H → 1H → 15m). Canonical name is exactly `multi_timeframe_analysis` (there is no "get_multi_timeframe_analysis" tool). Use this for cross-timeframe trend alignment on ONE symbol; for a single-timeframe deep dive use `coin_analysis`; for TA + sentiment + news use `combined_analysis`. Example: multi_timeframe_analysis(symbol="SOLUSDT", exchange="BINANCE") Args: symbol: Bare ticker, no exchange prefix — crypto: "BTCUSDT"; stocks: "COMI" (EGX), "THYAO" (BIST), "600519" (SSE), "300251" (SZSE), "2330" (TWSE), "3105" (TPEX), "GDX" (AMEX) exchange: Exchange — crypto: KUCOIN, BINANCE, MEXC; stocks: EGX, BIST, NASDAQ, NYSE, AMEX, NYSEARCA, PCX, SSE, SZSE, TWSE, TPEX, EPA (Euronext Paris), AMS, BRU, LIS, MIL, LSE, SIX, BME, XETRA, FWB, TSX, TSXV, NSE, BSE (India), IDX (Indonesia)

NameTypeReqDescription
exchangestring––
symbolstringyes–

No output schema declared.

No examples provided.

my_watchlist ~77

Show the user's personal watchlist. By default also fetches live prices + daily % change for every symbol on it (one batched request). Start here whenever the user says 'my watchlist', 'my list', or 'my coins/stocks'.

NameTypeReqDescription
include_quotesboolean–Fetch live prices for the list (default true).

No output schema declared.

No examples provided.

price_chart ~211

Render an interactive candlestick chart for a symbol inside the conversation. Accepts crypto pairs (BTCUSDT, BTC-USD), stocks (AAPL, NVDA) or any Yahoo Finance symbol. period: 1mo|3mo|6mo|1y|2y (1h also takes 1d|5d), interval: 1d|1h|15m. 15m charts show recent action only: period is limited to 1d|5d|1mo (longer values auto-adjust to 5d) and the most recent 350 bars are drawn. Set bollinger=true to overlay Bollinger Bands (SMA20 ± 2σ); the latest band values are returned in the result. Clients without interactive app support can read the `summary` field of the result.

NameTypeReqDescription
bollingerboolean––
intervalstring––
periodstring––
symbolstringyes–

No output schema declared.

No examples provided.

rating_filter ~198

Filter coins by Bollinger Band rating. Args: exchange: Exchange name like KUCOIN, BINANCE, BYBIT, MEXC, etc. timeframe: One of 5m, 15m, 1h, 4h, 1D, 1W, 1M rating: BB rating (-3 to +3): -3=Strong Sell, -2=Sell, -1=Weak Sell, 1=Weak Buy, 2=Buy, 3=Strong Buy limit: Number of rows to return (max 50) Returns ``list[dict]`` on success. On ANY failure returns a structured error envelope ``{"error": {"code": ..., "retryable": ...}}``.

NameTypeReqDescription
exchangestring––
limitinteger––
ratinginteger––
timeframestring––
NameTypeReqDescription
result–yes–

No examples provided.

smart_money_analysis ~389

Banker/hot-money proxy read for one symbol from price+volume history. Three independent families, computed from Yahoo Finance OHLCV: - mcdx_style: RSI-horizon decomposition (banker RSI50 / hot-money RSI40 / retail RSI14, each scaled 0-20) — sustained slow-horizon strength that fast horizons can't fake reads as institutional accumulation. - banker_fund_oscillator: EMA(13)-smoothed 34-bar stochastic of the weighted typical price, 0-100, with BANKER_ENTRY/EXIT states. - volume_flow_composite: CMF(20) + MFI(14) + OBV trend + up/down volume balance → 0-100 accumulation score. Plus a consensus vote across the three. These are documented, reproducible formula variants inspired by the public "banker fund" indicator family — NOT actual institutional-flow data, and not copies of any closed-source script. Args: symbol: Bare ticker — EGX: "COMI", "TMGH"; US: "AAPL"; crypto pairs work via Yahoo notation ("BTC-USD"). exchange: EGX (maps to Yahoo .CA), BIST (.IS), TADAWUL (.SR); anything else passes the symbol to Yahoo unchanged, except spot metals (XAUUSD on OANDA → gold futures GC=F; the result's `note` says so). period: 1mo | 3mo | 6mo | 1y | 2y (default 6mo) interval: 1d (default) or 1h

NameTypeReqDescription
exchangestring––
intervalstring––
periodstring––
symbolstringyes–

No output schema declared.

No examples provided.

smart_volume_scanner ~179

Smart volume + technical analysis combination scanner. Args: exchange: Exchange name min_volume_ratio: Minimum volume multiplier (default 2.0) min_price_change: Minimum price change percentage (default 2.0) rsi_range: "oversold" (<30), "overbought" (>70), "neutral" (30-70), "any" limit: Number of results (max 30) Returns ``list[dict]`` on success. On ANY failure returns a structured error envelope ``{"error": {"code": ..., "retryable": ...}}``.

NameTypeReqDescription
exchangestring––
limitinteger––
min_price_changenumber––
min_volume_rationumber––
rsi_rangestring––
NameTypeReqDescription
result–yes–

No examples provided.

stock_extended_hours ~297

Real-time pre-market and after-hours prices for a US stock symbol. Use this when the user asks about a stock outside the regular 9:30am-4pm ET session — earnings reactions, overnight news, "what is X doing in after-hours?", "how did Y open in pre-market?". Returns the most recent valid print from each session window (pre-market, regular, post-market) along with computed % changes vs. the previous close and the regular close, respectively. During the regular session, post_market will be null (no data yet). On weekends/holidays, returns whatever's most recent in each window. Args: symbol: US stock symbol — AAPL, NVDA, TSLA, SPY, ^GSPC, etc. Returns: - pre_market: {price, as_of_utc, change_vs_previous_close_pct, reference_close} or null; the change is measured from reference_close, the last regular close (before the open that is newer than previous_close) - regular: {price, as_of_utc, change_pct} (consolidated tape close) - post_market: {price, as_of_utc, change_vs_regular_close_pct} or null - previous_close, currency, exchange, market_state for context

NameTypeReqDescription
symbolstringyes–

No output schema declared.

No examples provided.

stock_options_chain ~255

Full options chain (calls + puts) for a US stock symbol and one expiry. Use this when the user asks "what's the options chain for X?", "show me AAPL puts expiring next Friday", or wants to inspect bid/ask/IV/volume on a specific strike. If no expiry is provided, returns the nearest expiry so Claude can quote it back and ask "want a different one?". Args: symbol: US stock symbol — AAPL, NVDA, TSLA, SPY, etc. expiry: Optional ISO date (YYYY-MM-DD). Must match one of the `available_expiries` Yahoo returns; otherwise returns an error with the list of valid dates. Returns: - underlying_price, underlying_change_pct - requested_expiry, available_expiries (list of YYYY-MM-DD) - call_count, put_count - calls: list of {strike, last_price, bid, ask, volume, open_interest, implied_volatility, in_the_money, expiration} - puts: same shape as calls

NameTypeReqDescription
expiry–––
symbolstringyes–

No output schema declared.

No examples provided.

stock_options_unusual_activity ~398

Top strikes by volume / open-interest ratio — institutional positioning signal. Use this when the user asks "any unusual options activity on X?", "where is the smart money positioned on NVDA before earnings?", or wants a V/OI screener for a ticker. A V/OI ratio > 1 means today's volume already exceeds standing open interest, which classically flags fresh institutional positioning on a specific strike in a specific direction (call vs put). Scans the soonest few expirations, filters out illiquid strikes (under `min_volume`), and returns the top-N sorted by V/OI descending. Also returns aggregate call vs put volume so Claude can comment on the overall directional bias. Args: symbol: US stock symbol — AAPL, NVDA, TSLA, SPY, META, etc. top_n: How many strikes to return. Default 10. min_volume: Filter floor for today's volume — prevents noise from illiquid strikes with high V/OI ratios. Default 100. expiries: Number of soonest expirations to scan. Default 4 (typically covers ~1 month of weeklies + monthlies). Returns: - underlying_price - expiries_scanned (list of YYYY-MM-DD) - total_call_volume, total_put_volume, put_call_volume_ratio - unusual: list of top-N contracts sorted by V/OI desc, each with {strike, side (call|put), expiration, volume, open_interest, v_oi_ratio, last_price, implied_volatility, in_the_money, strike_vs_spot_pct (moneyness)}

NameTypeReqDescription
expiriesinteger––
min_volumeinteger––
symbolstringyes–
top_ninteger––

No output schema declared.

No examples provided.

stock_prices ~149

Current price + daily % change for specific stock symbols. Args: tickers: comma-separated EXCHANGE:SYMBOL list (max 2000 — one upstream request even at full size), e.g. "NASDAQ:NVDA, NASDAQ:TSLA, KRX:005930". The exchange prefix is required — the scanner's direct-ticker lookup is exchange-scoped. Returns: Envelope dict: rows of {ticker, symbol, description, exchange, price, open, high, low, currency, change_percent} plus a not_found list naming any requested ticker the scanner didn't recognize.

NameTypeReqDescription
tickersstringyes–

No output schema declared.

No examples provided.

stock_screener ~381

Screen stocks by share type — the API twin of TradingView's "Common stock" / "Preferred stock" symbol-search filter. Args: country: TradingView market name — e.g. america, korea, germany, brazil, japan, uk, india, turkey, canada, australia, france, hongkong stock_type: common | preferred limit: rows to return (max 2000, single upstream request), ranked by market cap descending exclude_otc: default True — drop OTC listings (foreign companies traded over-the-counter); "america" otherwise means "US venue", not "US company" compact: default False — True returns only ticker/symbol/price/currency/ change_percent per row (light payload for bulk price feeds) sort_by: market_cap (default) | dividend_yield | change | price — server-side descending sort over the WHOLE market, so e.g. sort_by=dividend_yield with limit=20 is the market's true top-20 dividend payers, not just the biggest companies re-sorted Returns: Envelope dict: total_matches (market-wide count), returned, and rows of {ticker, symbol, description, exchange, price, open, high, low, currency, change_percent, dividend_yield, market_cap} — price is the current/last close; open/high/low are the current session's daily bar. Prices are in the market's local currency (e.g. KRW for korea).

NameTypeReqDescription
compactboolean––
countrystring––
exclude_otcboolean––
limitinteger––
sort_bystring––
stock_typestring––

No output schema declared.

No examples provided.

symbol_mentions ~46

Typeahead search for @-mentions: tickers on NASDAQ, NYSE, BIST and Binance as EXCHANGE:SYMBOL references.

NameTypeReqDescription
querystring––

Structured output declared, but exposes no named fields.

No examples provided.

top_gainers ~241

Return top gainers for an exchange and timeframe using Bollinger Band analysis. Args: exchange: Exchange name — crypto: KUCOIN, BINANCE, BYBIT, MEXC; stocks: EGX, BIST, NASDAQ, NYSE, BURSA, HKEX, SSE, SZSE, TWSE, TPEX, EPA (Euronext Paris), AMS, BRU, LIS, MIL, LSE, SIX, BME, XETRA, FWB, TSX, TSXV, NSE, BSE (India), IDX (Indonesia) timeframe: One of 5m, 15m, 1h, 4h, 1D, 1W, 1M limit: Number of rows to return (max 50) Returns: list[dict] on success. On ANY failure returns a structured error envelope ``{"error": {"code": ..., "retryable": ...}}`` — never a raw exception string.

NameTypeReqDescription
exchangestring––
limitinteger––
timeframestring––
NameTypeReqDescription
result–yes–

No examples provided.

top_losers ~104

Return top losers for an exchange and timeframe. Supports crypto (KUCOIN, BINANCE, MEXC) and stocks (EGX, BIST, NASDAQ). Returns ``list[dict]`` on success. On ANY failure returns a structured error envelope ``{"error": {"code": ..., "retryable": ...}}``.

NameTypeReqDescription
exchangestring––
limitinteger––
timeframestring––
NameTypeReqDescription
result–yes–

No examples provided.

volume_breakout_scanner ~227

Detect coins with volume breakout + price breakout. Args: exchange: Exchange name like KUCOIN, BINANCE, BYBIT, MEXC, etc. timeframe: One of 5m, 15m, 1h, 4h, 1D, 1W, 1M volume_multiplier: How many times the volume should be above normal level (default 2.0) price_change_min: Minimum price change percentage (default 3.0) limit: Number of rows to return (max 50) Returns ``list[dict]`` on success, or an error envelope on total upstream failure (``{"error": {"code": "ALL_BATCHES_FAILED", ...}}``). The empty list now strictly means "no matches today"; rate-limit cliffs surface explicitly.

NameTypeReqDescription
exchangestring––
limitinteger––
price_change_minnumber––
timeframestring––
volume_multipliernumber––
NameTypeReqDescription
result–yes–

No examples provided.

volume_confirmation_analysis ~70

Detailed volume confirmation analysis for a specific coin. Args: symbol: Coin symbol (e.g., BTCUSDT) exchange: Exchange name timeframe: Time frame for analysis

NameTypeReqDescription
exchangestring––
symbolstringyes–
timeframestring––

No output schema declared.

No examples provided.

walk_forward_backtest_strategy ~322

Walk-forward backtest to detect overfitting — validates strategy on unseen data. Args: symbol: Yahoo Finance symbol (AAPL, BTC-USD, SPY…) strategy: rsi | bollinger | macd | ema_cross | supertrend | donchian | keltner_breakout (rsi_pullback and triple_ema not supported here — SMA200 warmup exceeds typical fold size; use run_backtest with period='2y') period: '1mo', '3mo', '6mo', '1y', '2y' (recommend '2y') initial_capital: Starting capital per fold in USD (default $10,000) commission_pct: Per-trade commission % (default 0.1%) slippage_pct: Per-trade slippage % (default 0.05%) n_splits: Number of walk-forward folds (default 3, max 10) train_ratio: Fraction of each fold used for training (default 0.7) interval: '1d' (daily) or '1h' (hourly)

NameTypeReqDescription
commission_pctnumber––
initial_capitalnumber––
intervalstring––
n_splitsinteger––
periodstring––
slippage_pctnumber––
strategystringyes–
symbolstringyes–
train_rationumber––

No output schema declared.

No examples provided.

watchlist_add ~122

Add symbols to the user's personal watchlist (stored server-side, follows their API key across Claude/ChatGPT/any MCP client; max 50 symbols). Tickers must be EXCHANGE:SYMBOL, comma-separated — e.g. 'KUCOIN:BTCUSDT, NASDAQ:NVDA, BIST:THYAO, COMEX:GC1!'. Mixing asset classes is fine — crypto, stocks, futures, FX in one list.

NameTypeReqDescription
tickersstringyesComma-separated EXCHANGE:SYMBOL list to add.

No output schema declared.

No examples provided.

watchlist_remove ~90

Remove symbols from the user's personal watchlist. Tickers must be EXCHANGE:SYMBOL, comma-separated — e.g. 'KUCOIN:BTCUSDT, NASDAQ:NVDA, BIST:THYAO, COMEX:GC1!'. Removing is reversible (just add again).

NameTypeReqDescription
tickersstringyesComma-separated EXCHANGE:SYMBOL list to remove.

No output schema declared.

No examples provided.

yahoo_price ~137

Real-time price quote from Yahoo Finance for any stock, crypto, ETF or index. Yahoo has no spot gold, silver, platinum or palladium (XAUUSD=X, XAGUSD, OANDA:XPTUSD…): those are quoted from the front-month futures (GC=F, SI=F, PL=F, PA=F), and the result's `note` says so. Args: symbol: Yahoo Finance symbol — e.g. AAPL, BTC-USD, SPY, ^GSPC, EURUSD=X, THYAO.IS

NameTypeReqDescription
symbolstringyes–

No output schema declared.

No examples provided.

Install

How do I install the TradingMCP MCP server?

TradingMCP is a hosted endpoint at https://mcp.cryptosieve.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.cryptosieve.com

# add to Claude Code
claude mcp add --transport http atilaahmettaner-tradingview-mcp 'https://mcp.cryptosieve.com/mcp'
Common questions

What is the TradingMCP MCP server?

TradingMCP is an MCP server listed in the public MCP registry as io.github.atilaahmettaner/tradingview-mcp. Market analysis for AI assistants: screeners, multi-timeframe analysis, backtests, in-chat charts. This page covers its hosted endpoint (https://mcp.cryptosieve.com/mcp).

Is the TradingMCP MCP server safe to use?

TradingMCP scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the TradingMCP MCP server expose?

TradingMCP exposes 46 tools: price_chart, backtest_chart, markets_dashboard, symbol_mentions, top_gainers, and 41 more. Their descriptions and schemas cost roughly 8,652 tokens of context every time the server is loaded.

Does the TradingMCP MCP server require authentication?

No. We connected to TradingMCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the TradingMCP MCP server still maintained?

TradingMCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the TradingMCP MCP server?

VerifyMCP ran 14 checks on TradingMCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.