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.

TradingCalc MCP: Options, Forex, Risk Stats, Prediction Markets, On-Chain & Crypto Futures

REMOTE · TRADINGCALC.IO

Deterministic options, forex, risk, on-chain & futures math. Not AI estimates. Tools: tradingcalc.io

Available components

0 this week 86 Trust /100

Last scanned (23 hours ago)

Scores higher than 88% 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 Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 46501 tokens (~465/item across 100 items; 100 tools + 0 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 100 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 101 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

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

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.

  • 12 Nov 26 +3
    • Schema quality: unverified → 100 ▲ functional
    • The server now declares the “prompts” capability functional
    • New prompt “average_down” functional
    • New prompt “black_scholes” functional
    • New prompt “dsr” functional
    • New prompt “fibonacci_levels” functional
    • New prompt “forex_position_size_live” functional
    • New prompt “impermanent_loss” functional
    • New prompt “monte_carlo” functional
    • New prompt “odds_converter” functional
    • New prompt “option_greeks” functional
    • New prompt “risk_reward” functional
  • 10 Nov 26 0
    • Tool “workflow.run_cross_venue_arbitrage” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_liquidation_safety” rewrote its description, which is the text the model reads security
    • “workflow.run_cross_venue_arbitrage” added an optional parameter “feeFractionPerLeg” cosmetic
    • “primitive.hedge_ratio” reworded the description of “fundingRatePct” cosmetic
    • “workflow.run_compound_funding” reworded the description of “fundingRatePct” cosmetic
    • “workflow.run_cross_venue_arbitrage” reworded the description of “feePctPerLeg” cosmetic
    • “workflow.run_funding_breakeven” reworded the description of “funding_rate” cosmetic
    • “workflow.run_funding_cost” reworded the description of “fundingRate” cosmetic
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “primitive.average_entry” rewrote its description, which is the text the model reads security
    • Tool “primitive.hedge_ratio” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_american_option” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_apy_apr_converter” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_average_down” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_barrier_touch” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_black_scholes” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_black_scholes_live” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_bond_price” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_bonding_curve” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_breakeven_planning” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_breakout_acceptance” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_cagr” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_carry_trade” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_cash_secured_put” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_cointegration” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_compound_funding” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_covered_call_protective_put” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_cross_venue_arbitrage” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_crypto_profit” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_dca_entry” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_dsr” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_event_study” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_evt_tail_risk” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_exit_target” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_fibonacci_levels” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_average_entry” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_breakeven” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_correlation” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_correlation_live” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_currency_converter” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_currency_converter_live” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_margin_level” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_margin_required” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_margin_required_live” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_pip_value” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_pip_value_live” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_pnl” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_position_size_live” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_risk_reward” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_scenario” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_swap_cost” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_swap_cost_live” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_funding_arbitrage” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_funding_breakeven” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_funding_cost” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_future_value” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_garch” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_hurst_exponent” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_impermanent_loss” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_impermanent_loss_live” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_implied_volatility” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_irr” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_kelly_frontier” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_ladder_max_leg” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_liquidation_live” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_liquidation_safety” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_market_cap_comparison” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_market_implied_odds” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_max_leverage” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_monte_carlo” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_npv” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_odds_converter” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_open_analysis” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_option_greeks” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_options_payoff” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_options_position” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_orderbook_impact” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_pnl_planning” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_portfolio_risk” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_portfolio_tearsheet” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_position_sizing” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_pre_trade_check” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_prediction_market_edge” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_present_value” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_price_consensus” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_risk_parity” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_risk_reward” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_scale_out” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_scenario_planning” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_session_structure” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_sharpe_stats” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_spread_payoff” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_spread_reader” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_straddle_strangle” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_strategy_picker” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_swap_price_impact” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_token_risk_check” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_unsmoothing” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_value_migration” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_var_cvar” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_wallet_flag_check” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_window_fair_value” rewrote its description, which is the text the model reads security
    • Schema quality: 358 → 462 ▼ functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
    • Server version: 2.16.0 → 2.17.0 functional
    • New tool “workflow.run_average_buy_price” functional
    • New tool “workflow.run_max_pain” functional
    • New tool “workflow.run_spot_dca” functional
    • New tool “workflow.run_target_sell_price” functional
    • “workflow.run_carry_trade” reworded the description of “funding_rate_long” cosmetic
    • “workflow.run_carry_trade” reworded the description of “funding_rate_short” cosmetic
  • 5 Nov 26 0
    • Tool “workflow.run_liquidation_safety” rewrote its description, which is the text the model reads security
    • New tool “workflow.run_event_study” functional
    • New tool “workflow.run_ladder_max_leg” functional
  • 4 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “system.verify” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_liquidation_safety” rewrote its description, which is the text the model reads security
    • New tool “workflow.run_liquidation_live” functional
    • “workflow.run_liquidation_safety” added an optional parameter “otherMaintenanceMargin” cosmetic
    • “workflow.run_liquidation_safety” added an optional parameter “otherUnrealizedPnl” cosmetic
    • “workflow.run_liquidation_safety” added an optional parameter “size” cosmetic
    • “workflow.run_liquidation_safety” added an optional parameter “tiers” cosmetic
    • “workflow.run_liquidation_safety” added an optional parameter “walletBalance” cosmetic
    • “workflow.run_liquidation_safety” reworded the description of “contractType” cosmetic
    • “workflow.run_liquidation_safety” reworded the description of “liqFeeRate” cosmetic
    • “workflow.run_liquidation_safety” reworded the description of “mmBase” cosmetic
  • 3 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “system.verify” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_covered_call_protective_put” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_average_entry” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_forex_margin_required” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_liquidation_safety” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_options_payoff” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_spread_payoff” rewrote its description, which is the text the model reads security
    • Tool “workflow.run_straddle_strangle” rewrote its description, which is the text the model reads security
    • New tool “system.batch” functional
    • New tool “workflow.run_cash_secured_put” functional
    • “workflow.run_average_down” added an optional parameter “liqFeeRate” cosmetic
    • “workflow.run_average_down” added an optional parameter “mmBase” cosmetic
    • “workflow.run_covered_call_protective_put” added an optional parameter “exchange” cosmetic
    • “workflow.run_covered_call_protective_put” added an optional parameter “premiumUsdt” cosmetic
    • “workflow.run_options_payoff” added an optional parameter “exchange” cosmetic
    • “workflow.run_options_payoff” added an optional parameter “premiumUsdt” cosmetic
    • “workflow.run_pre_trade_check” added an optional parameter “liqFeeRate” cosmetic
    • “workflow.run_pre_trade_check” added an optional parameter “mmBase” cosmetic
    • “workflow.run_risk_reward” added an optional parameter “liqFeeRate” cosmetic
    • “workflow.run_risk_reward” added an optional parameter “mmBase” cosmetic
    • “workflow.run_spread_payoff” added an optional parameter “exchange” cosmetic
    • “workflow.run_straddle_strangle” added an optional parameter “callPremiumUsdt” cosmetic
    • “workflow.run_straddle_strangle” added an optional parameter “exchange” cosmetic
    • “workflow.run_straddle_strangle” added an optional parameter “putPremiumUsdt” cosmetic
    • “workflow.run_average_down” reworded the description of “mmr” cosmetic
    • “workflow.run_covered_call_protective_put” reworded the description of “currency” cosmetic
    • “workflow.run_covered_call_protective_put” reworded the description of “premiumCoin” cosmetic
    • “workflow.run_options_payoff” reworded the description of “currency” cosmetic
    • “workflow.run_options_payoff” reworded the description of “premiumCoin” cosmetic
    • “workflow.run_portfolio_risk” reworded the description of “positions” cosmetic
    • “workflow.run_risk_reward” reworded the description of “mmr” cosmetic
    • “workflow.run_spread_payoff” reworded the description of “currency” cosmetic
    • “workflow.run_spread_payoff” reworded the description of “legs” cosmetic
    • “workflow.run_straddle_strangle” reworded the description of “callPremiumCoin” cosmetic
    • “workflow.run_straddle_strangle” reworded the description of “currency” cosmetic
    • “workflow.run_straddle_strangle” reworded the description of “putPremiumCoin” cosmetic
    • “workflow.run_covered_call_protective_put” made “premiumCoin” optional cosmetic
    • “workflow.run_options_payoff” made “premiumCoin” optional cosmetic
    • “workflow.run_straddle_strangle” made “callPremiumCoin” optional cosmetic
    • “workflow.run_straddle_strangle” made “putPremiumCoin” optional cosmetic
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://tradingcalc.io/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tradingcalc.io CN=YR1,O=Let's Encrypt,C=US 10 Nov 2026 8 Feb 2027 RSA 2048 SHA256-RSA 5ef48cb070990ddfb698efb6ff4bf6ddc5c
SANs: tradingcalc.io
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tradingcalc.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
tradingcalc.io. 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=63072000
content-security-policy frame-ancestors 'self'
x-frame-options SAMEORIGIN

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tradingcalc.io/api/mcp Verified 200
http (plaintext) http://tradingcalc.io/api/mcp HTTPS enforced 308 https://tradingcalc.io/api/mcp
MCP tools · 100 exposed · ~45,659 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
workflow.run_spread_reader ~404

Reads the same real-world bet's live price from 2-5 prediction-market venues at once (Kalshi, Polymarket, ADI Predictstreet, Limitless, Myriad) in a single call and reports the spread between the cheapest and most expensive. Takes every venue's identifier together in quotes[], for example one Kalshi ticker and one Polymarket slug for the same bet, and returns the venue with the lowest yes midpoint price, before fees and depth. The caller supplies each venue's own identifier for what they've confirmed is the same underlying bet; this tool never auto-matches events across venues, only reads and compares prices for identifiers you provide. For the odds, breakeven win rate or vig of a single market, see workflow.run_odds_converter. Edge cases: 2 to 5 quotes; each venue is kalshi, polymarket, adi, limitless or myriad with a non-empty identifier; a venue that cannot be read comes back with available false and an error, and spreadPct is null when fewer than 2 quotes resolved. Prices are midpoints, before fees and depth. Not covered: confirming that the identifiers are the same bet (you confirm that), fees, order book depth, and whether the spread can be traded. Use when user asks "is this bet priced differently on Kalshi vs Polymarket?" or "which venue quotes the lowest yes price on this?". Returns: quotes[] (venue, identifier, label, probabilityPct, available, error), availableCount, cheapestVenue, mostExpensiveVenue, spreadPct (percentage points, null if fewer than 2 quotes resolved).

NameTypeReqDescription
quotesarrayyesOne entry per venue you want to compare: 2 to 5 total, all in this one call (a Kalshi ticker and a Polymarket slug for the same bet are two entries). Each must genuinely be the same real-world bet; t…

No output schema declared.

No examples provided.

workflow.run_straddle_strangle ~738

Payoff, P&L, and both breakeven prices for a long or short straddle/strangle (a call + a put on the same Deribit BTC/ETH underlying, both legs the same direction) at a scenario price. A straddle is callStrike === putStrike; any callStrike > putStrike makes it a strangle, same formula either way. Coin-settled like workflow.run_options_payoff: a long position's max loss is the flat total premium paid (between the strikes, both legs worthless); max profit is technically unbounded, dominated by the put leg's payoff as price falls toward zero. Edge cases: callStrike must be at or above putStrike; strikes, premiums and quantity above zero; for the Deribit coin-settled form callPremiumCoin plus putPremiumCoin must be below 1. Not covered: early exercise, margin, fees, Greeks and probability of profit; the result is the payoff at expiry at the one scenario price. Use when user asks about a straddle or strangle, e.g. "what does a BTC straddle pay off if price barely moves?" or "where are my breakevens on this strangle?". Returns: combinedIntrinsicCoin, scenarioPnlCoin, scenarioPnlUsd, upperBreakevenPrice, lowerBreakevenPrice, maxLossCoin/maxProfitCoin (null = unbounded), isStraddle, isProfitable. With exchange "binance" (USDT-settled, flat payoff, callPremiumUsdt and putPremiumUsdt) it returns: totalPremiumUsdt, combinedIntrinsicUsdt, scenarioPnlUsdt, upperBreakevenPrice (call strike + total premium), lowerBreakevenPrice (put strike - total premium, null when that is not above zero), maxLossUsdt/maxProfitUsdt (null = unbounded: the long side's profit is unlimited, the short side's loss is unlimited); USDT is not converted to USD.

NameTypeReqDescription
callPremiumCoinnumber–Deribit only. Call leg premium per contract, in the base coin (e.g. 0.02 BTC)
callPremiumUsdtnumber–Binance only. Call leg premium per unit, in USDT
callStrikenumberyesCall leg strike, USD. Equal to putStrike for a straddle, higher for a strangle.
currencystring–Underlying. Default BTC. XAU and XAG (gold, silver) only with exchange binance.
exchangestring–Venue whose settlement rules apply. "deribit" (default): BTC/ETH, coin-settled, premium in the base coin. "binance": BTC/ETH/XAU/XAG, USDT-settled, flat payoff max(0, S-K) per unit, premium in USDT (…
positionstringyesOption position: "long" (bought) or "short" (sold)
putPremiumCoinnumber–Deribit only. Put leg premium per contract, in the base coin
putPremiumUsdtnumber–Binance only. Put leg premium per unit, in USDT
putStrikenumberyesPut leg strike, USD. Must be <= callStrike.
quantitynumberyesNumber of straddle/strangle units (both legs sized equally)
scenarioPricenumberyesUnderlying price in USD to evaluate the payoff at

No output schema declared.

No examples provided.

workflow.run_strategy_picker ~684

Ranks option strategies for a price forecast and a volatility view. You give the spot price, the price you expect at expiry, days to expiry and the market implied volatility; optionally your own volatility forecast (default: the market's, so the view is on price only). Every strategy is built from strikes on a grid around spot, each leg priced with Black-Scholes at the one implied volatility (no skew, no dividends), and the best-fitting version of each family is kept: long call, long put, short put (cash-secured), covered call, protective put, long straddle, long strangle, bull call spread, bear call spread, bull put spread, bear put spread, long call butterfly, short iron condor, short iron butterfly; with allowUnlimitedLoss also naked short call, short straddle and short strangle. The view is a lognormal distribution whose mean is targetPrice and whose volatility is forecastVolPct. Per 1 unit of the underlying (multiply by contract size), each strategy returns its legs, net premium, max profit and max loss (null = unlimited), breakevens, expected profit under the view, probability of profit, and return on risk (expected profit / max loss). rankBy: expectedPnl (default), returnOnRisk (favours far out-of-the-money options) or probabilityOfProfit. Not a recommendation: the result is only as good as the forecast, and premiums are not discounted. Prices are computed, nothing is fetched; for equity options with quoted premiums use workflow.run_options_position. Edge cases: spot and targetPrice 1e-9 to 1e9; daysToExpiry above zero and at most 3650; impliedVolPct and forecastVolPct above zero and at most 1000; riskFreeRatePct 0 to 100; strikeStep above zero, and a step that gives fewer than 3 or too many strikes is an error with the step to use. Not covered: skew, dividends, early exercise, bid-ask spread, commissions, margin, taxes, and strategies with different expiries.

NameTypeReqDescription
allowUnlimitedLossboolean–Include naked short call, short straddle and short strangle. Default false.
daysToExpirynumberyesDays to expiry, above 0 and at most 3650
forecastVolPctnumber–Your own volatility forecast in percent per year. Default: impliedVolPct (no volatility view).
impliedVolPctnumberyesMarket implied volatility in percent per year (e.g. 30), used to price every option, at most 1000
rankBystring–Ranking key. Default expectedPnl.
riskFreeRatePctnumber–Annual risk-free rate in percent, 0 to 100. Default 0.
spotnumberyesCurrent price of the underlying, from 0.000000001 to 1000000000
strikeStepnumber–Strike spacing. Default: a round step that gives about 16 strikes across the range, plus one past each end. The grid must hold 3 to 60 strikes.
targetPricenumberyesPrice you expect at expiry (the mean of your view), from 0.000000001 to 1000000000

No output schema declared.

No examples provided.

workflow.run_swap_price_impact ~392

Live price-impact quote for a Solana token swap: routed through Jupiter (the same aggregator real swaps use) across every pool it knows about, not a single-pool estimate. Works in both directions: side "sell" (default) sells a token into USDC or SOL, side "buy" spends USDC or SOL to buy the token. Edge cases: mint a valid Solana base58 address (32 to 48 characters); amount above zero; side sell (default) or buy; outputAsset USDC (default) or SOL. Quotes come live from Jupiter and are a moment in time; an unknown token or no route returns routable false with an error and no figures. Solana only. Not covered: EVM swaps, MEV and sandwiching, priority fees, a price that moves between the quote and your swap, and tokens Jupiter cannot route. Use when user asks "how much slippage will I eat swapping X tokens?", "what will I actually get if I sell N tokens?" or "what do I get buying this token with 500 SOL?". Returns: side, outputAmount (quote asset when selling, tokens when buying), priceImpactPct, effectivePrice (quote asset per token in both directions), marketPriceUsd, liquidityUsd, routable (false + error if the size can't be routed at all).

NameTypeReqDescription
amountnumberyesAmount to swap, in human units (not raw base units): tokens when side is sell, units of outputAsset to spend when side is buy
mintstringyesSolana mint address of the token being sold or bought (base58)
outputAssetstring–The quote asset: received when selling, paid with when buying. Default USDC.
sidestring–sell: sell the token for outputAsset (default). buy: spend outputAsset to buy the token.

No output schema declared.

No examples provided.

workflow.run_target_sell_price ~611

The sell price that makes a target ROI or a target profit on a spot trade after both fees: the inverse of workflow.run_crypto_profit. Give exactly one of targetRoiPct (a fraction, 0.25 = 25%, negative for a stop price, above -1) or targetProfit (money; needs investment or quantity). Fees are a fraction of each fill's value (0.001 = 0.1%): the buy fee on top of the coins' cost, the sell fee out of the sale value (each fee at most 0.05); prices may be in any currency and results are in the same one; investment is the total cash spent, buy fee included. sellPrice = buyPrice x (1 + buyFee) x (1 + ROI) / (1 - sellFee); a target ROI of 0 is the break-even price. Edge cases: giving both or neither of targetRoiPct and targetProfit is an error; giving both investment and quantity is an error; targetProfit without a size is an error; a target that loses the whole stake or more (ROI of -1 or lower, or cost plus target profit at or below zero) is an error; a negative target gives a stop price below break-even. Not covered: taxes, FIFO/LIFO lots, slippage, withdrawal or network fees, currency conversion, leverage and funding. A target ROI does not depend on the size; with investment or quantity the cost, proceeds, profit and fees are returned too. Use when user asks "at what price do I sell to make 20% after fees?" or "to net $500 on this position, where do I put my limit sell?". Returns: sellPrice, requiredRoiPct (a fraction), priceChangePct, priceMultiple, breakevenSellPrice, and with a size: quantity, totalCost, sellValue, sellFee, proceeds, profit, totalFees (null without one).

NameTypeReqDescription
buyFeePctnumber–Buy fee as a fraction of the trade value, 0 to 0.05 (0.001 = 0.1%). Default 0
buyPricenumberyesPrice paid per coin
investmentnumber–Total cash spent on the buy, buy fee included. Give this or quantity, not both
quantitynumber–Number of coins bought. Give this or investment, not both
sellFeePctnumber–Sell fee as a fraction of the trade value, 0 to 0.05. Default 0
targetProfitnumber–Target profit in money after both fees (negative for a loss limit). Needs investment or quantity. Give this or targetRoiPct, not both
targetRoiPctnumber–Target return as a fraction of the cost (0.25 = 25%), above -1. Give this or targetProfit, not both

No output schema declared.

No examples provided.

workflow.run_token_risk_check ~320

Token rug-pull MECHANISM check for a Solana token (mint address): can the deployer still mint supply, freeze wallets, pull liquidity, swap metadata, or has RugCheck flagged a known scam pattern (e.g. copycat token)? Fetches live facts from RugCheck (GoPlus as fallback) and returns a transparently-weighted composite score. Deliberately does NOT score holder concentration or "whale dump" impact: those are properties of any liquid market (a legit protocol's top holders are routinely treasury/vesting/exchange wallets), not rug signals; they are returned separately as informational market_context. Edge cases: mint must be a Solana address; RugCheck is the main source and GoPlus the fallback, and when both fail the call returns an error rather than a score; a brand-new token may have no data yet. The score is a weighted read of public facts at one moment. Not covered: EVM tokens, holder concentration and whale dump risk (returned only as market_context), off-chain team behavior, future changes of authority, and any guarantee of safety. Use when user asks "is this token a rug pull?" or "is [token] safe to buy?". This is a sourced, timestamped read of public facts, not a safety guarantee. Returns: score (0-100), verdict (clean/caution/high_risk/red_flags), verdict_summary, components breakdown, facts, market_context, sources.

NameTypeReqDescription
mintstringyesSolana token mint address (base58)

No output schema declared.

No examples provided.

workflow.run_unsmoothing ~358

Return "unsmoothing" for infrequently-marked/illiquid or appraisal-based series: Getmansky-Lo-Makarov (2004) MA(2) smoothing index plus Blundell-Ward (1987) AR(1) volatility inflation, two complementary models answering "this return series looks smoother than it really is; what's the true volatility?". Edge cases: at least 20 returns; a flat series is an error; if the MA(2) fit does not converge from any starting point, or the lag-1 autocorrelation is 1 or more (Blundell-Ward inflation undefined), the call is an error. Not covered: more than 2 lags of smoothing, tax and fee effects, and proof that the smoothing comes from stale pricing rather than from the strategy. Use when user asks "how much is appraisal smoothing understating my real volatility?" or "what's my de-smoothed Sharpe ratio?". Returns: glm_theta (MA(2) weights), glm_smoothing_index (xi, 1=no smoothing, down to 1/3 for max MA(2) smoothing), glm_true_volatility_multiplier, glm_converged (false if the fit may be unreliable - treat that result with caution), bw_alpha (AR(1) coefficient = lag-1 autocorrelation, can be negative), bw_smoothing_detected (false when alpha<=0: no evidence of smoothing, bw_volatility_multiplier is then pinned to 1 with no correction applied rather than a misleading below-1 value), bw_volatility_multiplier, and each model's own true_stdev estimate.

NameTypeReqDescription
returnsarrayyesThe observed (possibly smoothed) return series, at least 20 values

No output schema declared.

No examples provided.

workflow.run_value_migration ~466

Market Profile value-area migration across sessions: is value migrating up, down, or overlapping (directional conviction vs balance)? Use for "is value moving higher day over day?". Returns: state, direction, migration_pct, key_levels (current vs. prior session VAH/VAL/VPOC), tails (session-high/low rejection tails and single prints), scenario_framing, invalidation level. Candles come from the venue when candles[] is omitted (past sessions are cached, so repeats are fast); supplying candles[] makes the run network-free and reproducible. session_date must be a completed UTC session, before today; a session with no candles returns an error. Edge cases: instrument non-empty and venue binance or bybit; session_date is a completed UTC session before today; timeframe 1m, 5m, 15m or 30m (default 15m); value_area_rule 0.5 to 0.9 (default 0.70); supplied candles must each have high at or above low, open and close, low at or below them, and volume 0 or more; a session with no candles is an error. lookback_sessions a whole number 1 to 5 (default 1). Not covered: order flow beyond the candles given, other venues, and any statement about what price will do; the output describes the session and is not a signal.

NameTypeReqDescription
candlesarray–Optional OHLCV for the session; omit to fetch from venue (reproducible + 0 COGS when supplied)
instrumentstringyesSymbol, e.g. BTCUSDT
lookback_sessionsnumber–Sessions to compare, 1–5 (default 1)
prev_candlesarray–Optional OHLCV for the previous session
session_datestringyesSession date YYYY-MM-DD (UTC); must be before today (a completed session)
timeframestring–Candle timeframe (default 15m)
value_area_rulenumber–Value-area fraction 0.5–0.9 (default 0.70)
venuestringyesExchange to fetch candles from when candles[] not supplied

No output schema declared.

No examples provided.

workflow.run_var_cvar ~463

Parametric Value at Risk (VaR) and Conditional VaR / Expected Shortfall (CVaR), the variance-covariance method (assumes normally distributed returns), plus Modified VaR (Cornish-Fisher skew/kurtosis correction, Boudt/Peterson/Croux) when a return series is supplied. Supply either a return series or a mean/stdev pair directly, at a confidence level. Output is at the same periodicity as the input (no automatic annualization) - a daily return series gives a daily VaR/CVaR. Edge cases: give returns (at least 2 values) or both mean and stdev (stdev zero or more), never neither; confidence strictly between 0 and 1 (default 0.95); Modified VaR needs at least 3 returns; a flat series (zero standard deviation) is an error. Not covered: historical or Monte Carlo VaR, fat tails beyond the Cornish-Fisher correction, portfolio aggregation, scaling to another horizon (the result stays in the period of the input). Use when user asks "what's my VaR at 95%/99%?", "what's my expected shortfall on this position?", or "does my Sharpe/VaR estimate need a fat-tails correction?". Returns: var, cvar (both positive loss magnitudes; cvar >= var always), z, mean, stdev, skewness, excess_kurtosis (both null unless 3+ returns were supplied), var_modified (skew/kurtosis-adjusted VaR; null when skewness is, OR when this series' skew/kurtosis are too extreme for the Cornish-Fisher expansion to be a valid quantile - skewness/excess_kurtosis are still returned in that case).

NameTypeReqDescription
confidencenumber–Confidence level, 0-1 exclusive (default 0.95)
meannumber–Mean return, if not supplying returns[] directly
returnsarray–Return series (e.g. daily % returns as decimals). Provide this OR mean+stdev, not both.
stdevnumber–Standard deviation of returns, if not supplying returns[] directly

No output schema declared.

No examples provided.

workflow.run_wallet_flag_check ~337

Checks a wallet address (Solana or any of 5 EVM chains) against independent flag databases: GoPlus (malicious-address categories, all chains), Webacy (address analysis + sanctions check, all chains), and ScamSniffer (public phishing/drainer blacklist, EVM chains only), and returns each source's own facts separately, never merged into one invented score. Edge cases: chain solana (default), ethereum, base, bsc, arbitrum or polygon; the address must fit the chain; ScamSniffer covers EVM chains only and is marked not applicable on Solana; a source that fails or has no key is reported as unavailable on its own and does not hide the others. No flag is not a clean bill of health. Not covered: wallets nobody has reported yet, transaction history, counterparty risk, and any legal or sanctions advice. Use when user asks "is this wallet address flagged?" or "is it safe to send to this address?". A clean result means "nothing found in these databases," not a certified-safe verdict. Returns: goplus (flags[], categoriesChecked), webacyGeneral (overallRisk, dprk/hack/ofacSanctioned, exchangeLabel), webacySanctions (status), scamSniffer (flagged; not applicable on Solana). Each source has an `available` flag: false + error if that source failed independently.

NameTypeReqDescription
chainstring–Chain of the wallet address. Default solana.
walletAddressstringyesWallet address (base58 for Solana, 0x... for EVM chains)

No output schema declared.

No examples provided.

workflow.run_window_fair_value ~486

Theoretical fair value for a time-windowed crypto up/down contract (the shape ADI Predictstreet and Kalshi-style daily crypto markets use: pays out based on whether the settlement price finishes at/above or below a reference price pinned at window open, by a fixed close time): a cash-or-nothing digital option, priced with the standard N(d2) formula. It gives the probability at the close time only, not the probability of touching a level at any point before it (first passage). Time convention: a year is 365 days. Use this when there's no live market price to read (e.g. a venue's contract has real terms but zero trading volume) instead of a live-market odds tool. Volatility is a required manual input; there is no live implied-vol market on these contracts to pull it from. Edge cases: currentPrice, referencePrice, minutesToClose and volatilityPct (annualized) above zero; riskFreeRatePct 0 to 100 (default 0); the volatility is yours, nothing is estimated; a year is 365 days. The result is the probability at the close only, not of touching the level before it. Not covered: first-passage (touch) probability, volatility that changes, jumps, the venue fees, order book prices, and the exact settlement rule of the venue. Use when user asks "what does the N(d2) model give for this up/down contract?" or "what's the model probability BTC finishes above $X in N minutes?". Returns: d1, d2, probAbovePct, probBelowPct, fairPriceAboveCents, fairPriceBelowCents (cents convention, directly comparable to how these venues quote a contract).

NameTypeReqDescription
currentPricenumberyesCurrent spot price of the coin, in USD.
minutesToClosenumberyesMinutes remaining until the window closes/settles.
referencePricenumberyesThe reference/pinned price the contract resolves against (the window's open price, or a stated strike).
riskFreeRatePctnumber–Risk-free rate in percentage points. Default 0: negligible for these short windows.
volatilityPctnumberyesAnnualized volatility, in percentage points (e.g. 50 for 50%). Required; no live source for this on these contracts.

No output schema declared.

No examples provided.

Install

How do I install the TradingCalc MCP: Options, Forex, Risk Stats, Prediction… server?

TradingCalc MCP: Options, Forex, Risk Stats, Prediction… is a hosted endpoint at https://tradingcalc.io/api/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 · tradingcalc.io

# add to Claude Code
claude mcp add --transport http skalinin909-tradingcalc 'https://tradingcalc.io/api/mcp'
Common questions

What is the TradingCalc MCP: Options, Forex, Risk Stats, Prediction… server?

TradingCalc MCP: Options, Forex, Risk Stats, Prediction… is listed in the public MCP registry as io.github.SKalinin909/tradingcalc. Deterministic options, forex, risk, on-chain & futures math. Not AI estimates. Tools: tradingcalc.io. This page covers its hosted endpoint (https://tradingcalc.io/api/mcp).

Is the TradingCalc MCP: Options, Forex, Risk Stats, Prediction… server safe to use?

TradingCalc MCP: Options, Forex, Risk Stats, Prediction… scores 86 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 TradingCalc MCP: Options, Forex, Risk Stats, Prediction… server expose?

TradingCalc MCP: Options, Forex, Risk Stats, Prediction… exposes 100 tools: workflow.run_pnl_planning, workflow.run_liquidation_safety, workflow.run_breakeven_planning, workflow.run_position_sizing, workflow.run_funding_cost, and 95 more. Their descriptions and schemas cost roughly 45,659 tokens of context every time the server is loaded.

Does the TradingCalc MCP: Options, Forex, Risk Stats, Prediction… server require authentication?

No. We connected to TradingCalc MCP: Options, Forex, Risk Stats, Prediction… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the TradingCalc MCP: Options, Forex, Risk Stats, Prediction… server still maintained?

TradingCalc MCP: Options, Forex, Risk Stats, Prediction… 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 TradingCalc MCP: Options, Forex, Risk Stats, Prediction… server?

VerifyMCP ran 13 checks on TradingCalc MCP: Options, Forex, Risk Stats, Prediction…, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.