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
primitive.average_entry ~290

Calculate the weighted average entry price from multiple buy/sell fills (DCA): the bare number only, no breakeven or per-fill breakdown. Edge cases: symbol non-empty; at least one fill, each price and quantity above zero (size is accepted as quantity); leverage above zero is optional. The average is weighted by quantity. Not covered: fees, sells or partial closes (give only the fills still open), and funding. Use when user asks only "what's my average entry?" and wants just that figure. Each fill is { price, quantity } here (workflow.run_dca_entry calls the same field size). For breakeven and a per-level summary too, use workflow.run_dca_entry instead. Returns: averagePrice, totalSize, totalCost.

NameTypeReqDescription
contractTypestring–linear = USDT-margined, average is the arithmetic mean (default). inverse = coin-margined, average is the harmonic mean (fill quantity is USD notional).
exchangeCodestring–Exchange identifier (optional)
inputobjectyesObject with a "fills" array, e.g. { "fills": [{ "price": 60000, "quantity": 0.5 }, { "price": 58000, "quantity": 1 }] }
symbolstringyesTrading pair symbol, e.g. BTCUSDT

No output schema declared.

No examples provided.

primitive.hedge_ratio ~553

Calculate the short perpetual futures position size needed to hedge a spot holding. Default USDT-linear: sizes and costs in USD. With contractType "inverse" (coin-margined, needs entryPrice) the short is the same USD contracts and margin and funding come back in the base coin. Edge cases: spotSize above zero (USD value); hedgeRatio 0 to 200 percent (default 100); leverage 1 or more (default 1); fundingRatePct in percent per interval (0.01 is 0.01%, default 0.01); intervalHours 0.25 to 24 (default 8); an inverse contract needs entryPrice. Not covered: basis risk between spot and the perp, rebalancing as prices move, margin calls, and a funding rate that changes. Use when user asks "how much should I short to hedge my BTC?" or "what margin do I need for a 100% hedge?". Returns: perpNotional, requiredMargin, dailyFundingCost, annualFundingCost, hedgeCoverage, contractType and costUnit ("USD", or "base_coin" for inverse: read it before showing margin or funding as dollars). Inverse converts at the one entryPrice you give, so the coin figures assume the price stays there.

NameTypeReqDescription
contractTypestring–linear = USDT-margined (default). inverse = coin-margined: spotSize stays the USD value of the holding, requiredMargin and the funding costs are returned in the base coin.
entryPricenumber–Coin price in USD. Required for contractType inverse (converts the USD margin and funding to coin); ignored for linear.
fundingRatePctnumber–Current funding rate per funding interval in PERCENT: 0.01 means 0.01%, so a quoted 0.0125% is 0.0125 (per 8h unless intervalHours says otherwise). Used for cost estimate.
hedgeRationumber–Percentage of spot to hedge, e.g. 100 for full hedge, 50 for half. Default 100.
intervalHoursnumber–Hours between funding payments, the period fundingRatePct covers. Default 8 (3 payments a day); 1 on Hyperliquid, dYdX, Kraken and Backpack (per-hour rates); 4 or 2 on some symbols of Binance, Bybit,…
leveragenumber–Leverage on the perp short. Default 1.
spotSizenumberyesSpot position value in USDT

No output schema declared.

No examples provided.

system.batch ~175

Run up to 10 calls of other tools in one request and get all results back together, in order. Each entry is {name, arguments} exactly as for a single call; each result carries its own signature block, so every one verifies on its own. The batch call itself is free: every entry counts as one call against the daily limit. A failed entry does not stop the others (it comes back with an error), except that once the daily limit is reached or the batch has run for about 20 seconds, the entries after that point are not run and not counted: the reply says so for each, so send them again. A batch cannot contain a batch. Entries run one after another, in order, and none sees the output of another.

NameTypeReqDescription
callsarrayyes1 to 10 calls

No output schema declared.

No examples provided.

system.pubkey ~76

Return the ECDSA P-256 public key (PEM + JWK) and canonical signing format used to sign tool responses, so results can be verified offline without calling back to TradingCalc. Every tools/call result includes a signed second content block when signing is configured; also available at GET /api/mcp/pubkey.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

system.verify ~60

Run the full regression suite: 60 canonical test vectors (linear and inverse/coin-margined) across all 12 calculators, and return a pass/fail report with counts and timestamp. Useful as a health check before relying on results in production workflows.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

workflow.run_american_option ~516

Price of an AMERICAN put or call (exercisable on any day up to expiry) on a Cox-Ross-Rubinstein binomial tree with early exercise checked at every node, with a continuous dividend yield. Use it for stock and ETF style options; crypto options on Deribit and Binance are European (`workflow.run_black_scholes`). Output: americanPrice, delta, gamma, thetaPerDay (calendar day, read from the tree, typically 0 when exercising now is optimal), intrinsicValue, earlyExerciseNow (a tree reading: exercising now beats holding), europeanPrice (Black-Scholes, same inputs), earlyExercisePremium, europeanTreePrice and treeError (what the chosen step count costs: the same tree without early exercise minus the exact European price). More steps are closer to the exact value, not smoothly. Rates 0 to 100 percent, dividend yield is a continuous yield, not dated dividends; steps are a whole number from 50 to 2000 (default 500). Prices are USD per unit of underlying. Edge cases: spot, strike, daysToExpiry (at most 3650) and volatilityPct (at most 300) above zero; steps a whole number from 50 to 2000; when the rate and the dividend yield are too far apart for the volatility and expiry the tree is invalid and the call is an error that says so; numbers that overflow are an error. The price is a tree value, close to the exact one but not equal to it (see treeError). Not covered: discrete dividends, a volatility smile, negative rates, taxes, margin, transaction costs, and exercise limited to certain dates (Bermudan).

NameTypeReqDescription
daysToExpirynumberyesCalendar days to expiry (up to 3650)
dividendYieldPctnumber–Continuous dividend yield in percent per year, 0 to 100. Default 0.
optionTypestringyesAmerican call or put
riskFreeRatePctnumber–Annual risk-free rate in percent, 0 to 100. Default 0.
spotnumberyesCurrent price of the underlying
stepsinteger–Binomial tree steps, whole number from 50 to 2000. Default 500.
strikenumberyesStrike price, same units as spot
volatilityPctnumberyesAnnualized volatility in percentage points (e.g. 30 for 30%), at most 300

No output schema declared.

No examples provided.

workflow.run_apy_apr_converter ~456

Convert an APR (nominal yearly rate) to an APY (effective yearly rate) or back, for a compounding you choose. APY = (1 + APR / m)^m - 1 for m periods a year, e^APR - 1 when continuous. The same APY is a different APR at every compounding frequency, so the frequency is required: give periodsPerYear (365 daily, 12 monthly) or continuous true, not both. Rates are fractions (0.12 = 12%). It converts rate arithmetic only: it does not include fees, token price moves or the risk that a pool rate changes. Edge cases: rate a fraction from -periodsPerYear (APR) or above -1 (APY) up to 1000; give periodsPerYear (1 to 365) or continuous true, never both and never neither; the rate per period must stay above -100%; a continuous APR above 709 (70,900%) is an error. Not covered: fees, token price moves, a pool rate that changes, taxes, and compounding that is not regular. Use when user asks "what APR is an 8% APY compounded daily?" or "what is 12% APR monthly as an APY?". Returns: apr, apy, periodsPerYear, continuous, ratePerPeriod, apyMinusApr, byCompounding (the same APY as an APR at annual, semiannual, quarterly, monthly, weekly, daily and continuous compounding).

NameTypeReqDescription
continuousboolean–True for continuous compounding; then omit periodsPerYear
directionstringyesapr_to_apy converts the given APR into an APY; apy_to_apr the reverse
periodsPerYearinteger–Compounding periods a year, 1 to 365 (12 monthly, 365 daily). Omit when continuous is true
ratenumberyesThe rate you have, as a fraction per year (0.12 = 12%), up to 1000. An APY must be above -1; an APR must satisfy APR / periodsPerYear above -1

No output schema declared.

No examples provided.

workflow.run_average_buy_price ~463

Real entry price of a spot coin bought and sold in several trades: moving average cost, trades in the order they happened, each with its own fee (no leverage, no funding). The buy fee is part of the cost basis; a sale removes coins at the current average and never changes the average of what is left, only a later buy does; selling everything resets it. Selling more than is held at that point is an error naming the trade. Each fee is a fraction of that trade's value (0.001 = 0.1%, at most 0.05). Edge cases: 1 to 1000 trades; price and quantity above zero; a sale before any buy, or above the holding, is an error; a sale within 1e-12 of the largest holding since the position was last flat counts as selling everything (float noise) and leaves exactly zero, never a residual; when nothing is held the average, before-fee average and break-even are null and costBasis is 0; realizedProfit can be negative. Not covered: taxes, FIFO/LIFO lots (moving average cost only), slippage, withdrawal or network fees, currency conversion, leverage and funding. Prices may be in any currency; results are in the same one. sellFeePct is the fee expected when the remaining coins are sold, used for the break-even sell price. For equal cash buys at a list of prices use workflow.run_spot_dca; for the average entry of a perpetual futures position use primitive.average_entry. Use when user asks "I bought and sold this coin several times, what is my average buy price and break-even now?". Returns: remainingQuantity, averageBuyPrice (fees in) and averageBuyPriceBeforeFees (null when nothing is held), costBasis, totalBought, totalSold, totalInvested, totalSellProceeds, realizedProfit, totalFees, breakevenSellPrice (null when nothing is held).

NameTypeReqDescription
sellFeePctnumber–Fee expected when the remaining coins are sold, 0 to 0.05, for the break-even sell price. Default 0
tradesarrayyesTrades in the order they happened (1 to 1000)

No output schema declared.

No examples provided.

workflow.run_average_down ~754

Should-I-average-down check: for an already-open position, compares adding more at a worse price against the always-available alternative of buying the same final total size fresh at today's price. Returns the new blended average entry, liquidation price and breakeven (before vs. after), margin_added (the actual cash/margin required for the add at this leverage, not the full notional), and three risk figures at your stop-loss: existing_risk (what you already risk, before adding), pyramid_risk (what you'd risk after adding), and clean_entry_risk (what a fresh entry at add_price for the same total size would risk). risk_penalty_pct is how much MORE than that fresh-entry alternative you're risking - for any genuine average-down (add_price worse than existing_entry_price) pyramid_risk is provably always greater than clean_entry_risk. liquidation_before_stop is true when the new liquidation price sits at or beyond your own stop-loss, meaning the exchange would force-close the position before the stop-loss ever triggers. Edge cases: all prices, sizes, stop_loss and leverage above zero; fee_open_pct and fee_close_pct are fractions from 0 to 0.05 (defaults 0.0002 and 0.0005); mmr 0 to 0.2; for a long the stop must be below the add price and for a short above it, otherwise an error (a stop that price already reached means the position should be closed). The risk comparison is meaningful only when the add is at a worse price than the existing entry. Not covered: funding, slippage, a stop that gaps through, and whether the market will recover. Use when user asks "should I add to this losing position?" or "what does averaging down actually cost me here?". liquidation_price and the liquidation distance are null when the position cannot be liquidated (an inverse short at 1x or less): check for null before using them.

NameTypeReqDescription
add_pricenumberyesProposed price to add at - also treated as today's current price for the fresh-entry comparison
add_sizenumberyesAdditional size being considered, same unit convention as existing_size
contractTypestring–linear = USDT-margined (default), inverse = coin-margined. Risk figures come back denominated in the base coin for inverse.
existing_entry_pricenumberyesEntry price of the position already held
existing_sizenumberyesSize already held: base-asset quantity for linear, USD notional (contracts) for inverse
fee_close_pctnumber–Close fee rate (default 0.0005)
fee_open_pctnumber–Open fee rate (default 0.0002)
leveragenumberyesLeverage multiplier
liqFeeRatenumber–Liquidation fee as a fraction of position value, default 0, max 0.05; added to mmr.
mmBasestring–Value the maintenance margin is taken on: "liquidation" = position value at the liquidation price (default), "entry" = entry value.
mmrnumber–Maintenance margin rate as a fraction, 0 to 0.2 (default 0.005 = 0.5%); not a percent: 0.5% is 0.005, not 0.5
sidestringyesTrade direction: "long" or "short"
stop_lossnumberyesStop-loss price (must be below add_price for a long, above it for a short - the position should already be closed otherwise)

No output schema declared.

No examples provided.

workflow.run_barrier_touch ~390

Probability that the price touches a barrier (a target or a stop level) at ANY time within N days, under geometric Brownian motion (reflection principle with drift). This is not the probability of finishing beyond the level at expiry: at zero log-drift a touch is exactly twice as likely as a finish, and `finishBeyondProbabilityPct` is returned next to it for comparison (the end-of-window question itself is `workflow.run_window_fair_value`). Barrier above spot gives an up-touch, below spot a down-touch. Monitoring is continuous (every instant, not daily closes or candle highs, which touch less often); year is 365 days; `driftPct` is the annualized expected price drift, default 0. Output: touchProbabilityPct, finishBeyondProbabilityPct, direction, barrierDistancePct. Edge cases: spot, barrier and daysToExpiry (at most 3650) above zero; volatilityPct 0.01 to 1000; driftPct -1000 to 1000; barrier and spot must be within a factor of about 5e8 of each other. Not covered: a discrete-monitored barrier, knock-in or knock-out option prices, jumps, volatility that changes over time, trading costs; the probability is under a constant volatility and drift.

NameTypeReqDescription
barriernumberyesThe level to touch, same units as spot. Above spot: up-touch; below spot: down-touch
daysToExpirynumberyesCalendar days in the window (can be fractional, up to 3650)
driftPctnumber–Annualized expected price drift in percentage points. Default 0.
spotnumberyesCurrent price, USD (any quote currency)
volatilityPctnumberyesAnnualized volatility in percentage points (e.g. 60 for 60%), at least 0.01

No output schema declared.

No examples provided.

workflow.run_black_scholes ~555

Theoretical European option price and Greeks (delta, gamma, theta, vega, rho) from Black-Scholes, given manual spot/strike/days-to-expiry/volatility/risk-free-rate inputs plus an optional continuous dividend yield for stocks and ETFs (the implied-volatility and option-chain tools do not take one): no live data fetch. The live variant is workflow.run_black_scholes_live, which applies when checking a real Deribit, Binance or Bybit instrument, since that variant also reports how far the instrument's actual quoted price sits from what this formula implies. Prices are USD-denominated (the universal convention); callPriceCoin/putPriceCoin additionally divide by spot to match Deribit's own coin-settled quoting convention. Assumptions: European exercise only, one flat volatility for the whole life (no smile or skew), constant rate and dividend yield, a year of 365 calendar days, theta per calendar day. Edge cases: spot, strike, daysToExpiry and volatilityPct must be above zero; riskFreeRatePct and dividendYieldPct must be between 0 and 100, so a negative rate is refused; a deep out-of-the-money option returns a price and Greeks of exactly 0, and a very low volatility or very short expiry gives a very large gamma and theta, not an error. Not covered: early exercise (use workflow.run_american_option), discrete dividends, negative rates, transaction costs, taxes, margin, and Greeks adjusted for coin-settled (inverse) options: Greeks are standard USD Black-Scholes Greeks. Use when user asks "what should this option be worth at X% IV?" or wants raw Greeks for a hypothetical. Returns: callPriceUsd/putPriceUsd, callPriceCoin/putPriceCoin, deltaCall/deltaPut, gamma, vegaPerPct (per 1 vol point), thetaCallPerDay/thetaPutPerDay, rhoCallPerPct/rhoPutPerPct (per 1 rate point).

NameTypeReqDescription
daysToExpirynumberyesCalendar days until expiry (can be fractional)
dividendYieldPctnumber–Continuous dividend yield in percent per year (1.2 means 1.2%), for stock and ETF options. Default 0: crypto has none. Range 0 to 100.
riskFreeRatePctnumber–Risk-free rate in percentage points. Default 0: standard crypto-options convention.
spotnumberyesUnderlying spot price, USD
strikenumberyesStrike price, USD
volatilityPctnumberyesAnnualized implied volatility in percentage points, e.g. 60 for 60%

No output schema declared.

No examples provided.

workflow.run_black_scholes_live ~858

Black-Scholes theoretical price and Greeks for a REAL, live option instrument on Deribit (BTC/ETH, coin-settled) Binance (BTC, ETH, XAU, XAG, USDT-settled) or Bybit (BTC, ETH, USDT-settled): pulls that instrument's own spot, strike, days to expiry, and implied volatility from the venue, then reports how far the venue's actual quoted mark price sits from what Black-Scholes implies at that IV (priceDiscrepancyPct). This is the trust-check tool: "is this exchange's quoted price consistent with its own volatility assumption?", not an estimate, a live formula cross-check. Edge cases: European Black-Scholes on the venue mark IV with one flat volatility; an expired instrument, a missing or zero mark IV, an invalid underlying price or a mark price of 0 returns available false with the reason, never a number (every numeric field is then null); riskFreeRatePct 0 to 100 applies to Deribit only (Binance states its own rate, Bybit prices off a forward with none). Not covered: early exercise, discrete dividends, skew, bid-ask spread and Greeks adjusted for coin settlement. Use when user gives a specific instrument name (e.g. "BTC-27FEB27-90000-C" on Deribit, "BTC-261225-90000-C" on Binance, "BTC-25DEC26-90000-C-USDT" on Bybit) and asks "is this option fairly priced?" or "what are the Greeks on this contract?". Returns everything workflow.run_black_scholes does, plus instrumentName, exchange, premiumCurrency (BTC/ETH for Deribit, USDT for Binance and Bybit), optionType, markPrice, markIvPct, bsPrice, priceDiscrepancyPct, available (false + error if the instrument name doesn't resolve, the contract has expired or has no IV quote, a Binance contract states no usable risk-free rate (missing or outside -100 to 100%), or a Binance or Bybit market is not trading; then do not use any result field, they are null; read available first). For Deribit also currency, deribitMarkPriceCoin, deribitMarkIvPct, bsPriceCoin; for Binance and Bybit those and the coin-quoted callPriceCoin/putPriceCoin…

NameTypeReqDescription
exchangestring–Venue of the instrument. Default deribit.
instrumentNamestringyesExact instrument name: Deribit BTC-27FEB27-90000-C, Binance BTC-261225-90000-C (expiry YYMMDD), Bybit BTC-25DEC26-90000-C-USDT (expiry DMMMYY). Get one from the venue's options chain; this tool does…
riskFreeRatePctnumber–Risk-free rate in percentage points, Deribit only. Default 0: standard crypto-options convention. Binance states its own rate for each contract and the price uses that one; a value here is not used f…

No output schema declared.

No examples provided.

workflow.run_bond_price ~539

Price of a plain fixed-rate bond on a coupon date, with Macaulay duration, modified duration, convexity and DV01. Price = sum of the coupons and the face value discounted at the yield per period (yield / frequency), clean price, no accrued interest, so years x frequency must be a whole number of coupon periods. The yield is the nominal yearly yield to maturity compounded frequency times a year (the bond-market convention). Durations are in years, convexity in years squared. DV01 is the price fall for one basis point of yield, a positive number, the slope at the current yield and not a repricing. It does not include credit risk, call features, taxes or the day-count of a real settlement date. Edge cases: faceValue above zero and at most 1e12 (default 1000); couponRate 0 to 1 as a fraction; yieldRate -1 to 100 with the rate per period above -100%; years above zero and at most 100; frequency a whole number 1 to 12 (default 2); years times frequency must be a whole number of coupon periods. Not covered: accrued interest and a settlement date between coupons, credit risk, call and put features, floating coupons, taxes, and the day-count convention. Use when user asks "what is a 5-year 5% coupon bond worth at a 6% yield?" or "what is the duration and DV01 of this bond?". Returns: price, pricePctOfFace, status (premium, par, discount), pvOfCoupons, pvOfFace, couponPerPeriod, periods, yieldPerPeriod, currentYield, macaulayDuration, modifiedDuration, convexity, dv01.

NameTypeReqDescription
couponRatenumberyesAnnual coupon rate as a fraction of face value (0.05 = 5%), 0 to 1; 0 is a zero-coupon bond
faceValuenumber–Face (par) value repaid at maturity, above 0 (default 1000)
frequencyinteger–Coupon payments a year, 1 to 12 (default 2: semiannual; 1 annual, 4 quarterly, 12 monthly)
yearsnumberyesYears to maturity, above 0 and at most 100; years x frequency must be a whole number (5 years semiannual is 10 coupons)
yieldRatenumberyesNominal yearly yield to maturity as a fraction (0.06 = 6%), compounded frequency times a year; yield / frequency must be above -1

No output schema declared.

No examples provided.

workflow.run_bonding_curve ~260

Pump.fun-style bonding curve calculator: exact tokens received for a buy, price impact, and graduation progress. Pure constant-product math (Uniswap V2 style) using pump.fun's official virtual-reserve constants: no live lookup needed, works for any token still on the curve (not yet graduated to a real AMM pool). Edge cases: solRaisedSoFar from 0 up to the graduation amount (a graduated token is out of range); solToSpend above zero. Pure constant-product math with pump.fun virtual-reserve constants, no live lookup. Not covered: the pump.fun trading fee unless stated in the result, slippage from other buyers landing first, tokens that already graduated to a real pool, and other launchpads with a different curve. Use when user asks "how many tokens do I get buying X SOL on this curve?" or "will this buy graduate the token?". Returns: tokensOut, priceImpactPct, progressPctBefore/After, willGraduate, partialFill (true if the buy exceeds remaining curve capacity).

NameTypeReqDescription
solRaisedSoFarnumberyesSOL already raised on the curve so far (0 for a brand-new token)
solToSpendnumberyesSOL amount for this buy

No output schema declared.

No examples provided.

workflow.run_breakeven_planning ~292

Calculate the break-even exit price that covers all trading fees: this alone, nothing else. Edge cases: entryPrice and sizeBase above zero; feeOpenPct and feeClosePct fractions from 0 to 0.05 (defaults 0.0002 and 0.0005). Fees only. Not covered: funding (use workflow.run_funding_breakeven), slippage and spread. Use when user asks only "what price do I need to just break even?" and nothing more. If the user also gave a stop/target or wants a full trade-safety check, use workflow.run_risk_reward or workflow.run_pre_trade_check instead; both already include this breakeven figure plus more. Returns: breakevenPrice, totalFees.

NameTypeReqDescription
contractTypestring–linear = USDT-margined (default), inverse = coin-margined. For inverse, totalFees is returned in the base coin.
entryPricenumberyesEntry price (positive)
feeClosePctnumber–Closing fee fraction, default 0.0005
feeOpenPctnumber–Opening fee fraction, default 0.0002
sidestringyesTrade direction: "long" or "short"
sizeBasenumberyesPosition size: base asset qty for linear, USD contracts for inverse

No output schema declared.

No examples provided.

workflow.run_breakout_acceptance ~451

Market Profile breakout acceptance: did price accept (hold) beyond the value area / range, or reject back inside (fakeout)? Optional buy/sell delta. Use for "did the break above VAH get accepted?". Returns: state, accepted (boolean), direction, confidence, key_levels (VAH/VAL/VPOC), 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. include_delta true or false (default true). 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)
include_deltaboolean–Include buy/sell delta analysis (default true)
instrumentstringyesSymbol, e.g. BTCUSDT
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_cagr ~284

Compound annual growth rate between a beginning and an ending value over a number of years: the constant yearly rate that turns one into the other, (ending / beginning)^(1 / years) - 1. A smoothed average: it hides the path and the volatility in between, and it says nothing about future growth. Both values must be positive. Edge cases: beginningValue and endingValue above zero (a start or end of zero or below has no growth rate); years above zero and at most 1000, a fraction of a year is fine. Not covered: contributions or withdrawals in between (that is not CAGR), the path and volatility between the two dates, and any forecast; CAGR smooths a bumpy path into one rate. Use when user asks "what is the CAGR of my portfolio?" or "what yearly growth takes $10,000 to $25,000 in 8 years?". Returns: cagr, totalReturn, growthMultiple, logGrowthRate (all fractions; logGrowthRate is the continuously compounded rate).

NameTypeReqDescription
beginningValuenumberyesValue at the start (positive)
endingValuenumberyesValue at the end (positive), same currency
yearsnumberyesYears between them, above 0 and at most 1000 (fractions allowed, e.g. 2.5)

No output schema declared.

No examples provided.

workflow.run_carry_trade ~420

Delta-neutral carry trade (funding arbitrage) analysis, with a profitable/marginal/loss verdict on top of the same math primitive.funding_arb uses. Compared with primitive.funding_arb, this one adds output for the case where a plain-English verdict is wanted, not just the raw numbers. Edge cases: notional and hold_days above zero; funding_rate_long and funding_rate_short are in PERCENT per interval (0.01 means 0.01%), either sign; transfer_fee_pct 0 or more, one way (default 0.1); interval_hours 0.25 to 24 (default 8), one interval for both legs. Not covered: price divergence between the two venues, liquidation of either leg, margin needed on both venues, rates that change during the hold, and withdrawal limits; the result assumes the rates stay as given. Use when user asks "is this carry trade worth it?": long on exchange A, short on exchange B, collect the funding rate spread. Returns: netYieldPct, grossProfit, netProfit, breakevenDays, verdict (profitable/marginal/loss).

NameTypeReqDescription
funding_rate_longnumberyesFunding rate on the long exchange per interval, in percent (0.01 means 0.01%, not 0.0001)
funding_rate_shortnumberyesFunding rate on the short exchange per interval, in percent (0.01 means 0.01%, not 0.0001)
hold_daysnumberyesHold duration in days
interval_hoursnumber–Hours between funding payments, one interval for both legs (default 8; 1 for hourly venues; 4 or 2 on some symbols). A leg paid on another interval is entered as its rate times (this interval / its o…
notionalnumberyesPosition notional in USDT
transfer_fee_pctnumber–One-way transfer fee % (default 0.1)

No output schema declared.

No examples provided.

workflow.run_cash_secured_put ~569

Cash-secured put on a US stock or ETF, in US dollars with the standard 100-share contract (NOT Deribit and not coin-settled): you sell puts and hold the cash to buy the shares if they are assigned. Returns the premium income, the cash held as collateral (strike x 100 x contracts), the return for the period (premium / collateral) and the simple annualized return by days to expiry (365-day year, not compounded), the effective buy price if assigned (strike minus premium, which is also the breakeven), the net cost of the shares if assigned, the maximum profit (the premium), the maximum loss (shares to zero) and the dollars lost per $1 the price falls below the breakeven. Optional spotPrice adds the discount to buying the shares now and the strike distance from the spot; optional scenarioPrice adds the P&L at expiry at that price, whether the put is assigned, and the same price move compared with buying the shares now at spotPrice. A scenario price exactly at the strike counts as not assigned (the P&L is the same either way). A premium at or above the strike is refused. The premium is the one you type (per share, as quoted); commissions, early assignment, taxes, dividends and interest on the cash are not modelled. Edge cases: strike above zero; premium 0 or more and below the strike; contracts a whole number from 1 to 1,000,000; daysToExpiry 1 to 3650; spotPrice above zero and scenarioPrice 0 or more when given. Not covered: a fractional contract, and (already stated) commissions, early assignment, taxes, dividends and interest on the cash. Use when the user asks what selling a cash-secured put pays, what price they would effectively buy at, or whether it beats buying the stock now. Prices are computed, nothing is fetched.

NameTypeReqDescription
contractsintegeryesNumber of contracts sold, a whole number from 1 to 1,000,000
daysToExpirynumberyesCalendar days to expiry, 1 to 3650
premiumnumberyesPremium received per share as quoted, USD, 0 or more and below the strike. A contract covers 100 shares, so 2.50 pays 250 dollars per contract.
scenarioPricenumber–Optional: a share price at expiry, USD, 0 or more, to report the P&L at
spotPricenumber–Optional: the share price today, USD, above 0, for the comparison with buying now
strikenumberyesStrike price of the put, USD per share, above 0

No output schema declared.

No examples provided.

workflow.run_cointegration ~269

Engle-Granger two-step cointegration test for a pair of price series: do they share a long-run equilibrium relationship (their spread is stationary/mean-reverting)? The standard pairs-trading signal test. Returns the cointegrating regression's hedge ratio (beta) and an ADF t-statistic on the residuals, compared against 1%/5%/10% critical values. Edge cases: x and y each at least 20 values and the same length, one observation per date (otherwise an error); constant residuals (zero variance) are an error; the test is one direction (y regressed on x), Engle-Granger. Not covered: more than two series (Johansen), structural breaks, a time trend in the regression, half-life of the spread, transaction costs, and any claim that the relation continues. Use when user asks "are these two assets cointegrated?" or "is this a valid pairs trade?". Returns: alpha, beta (hedge ratio), t_stat, critical_values, cointegrated (booleans at each significance level).

NameTypeReqDescription
xarrayyesSecond price series, same length and dates as y
yarrayyesFirst price series (the dependent variable in the cointegrating regression)

No output schema declared.

No examples provided.

workflow.run_compound_funding ~453

Project capital growth from reinvesting perpetual futures funding income (compounding carry). Edge cases: initialCapital above zero; fundingRatePct in percent per interval (0.01 is 0.01%), either sign; intervalHours a whole number that divides 24 (1, 2, 3, 4, 6, 8, 12 or 24, default 8); durationDays above zero and at most 3650; reinvestPct 0 to 100 (default 100); a result too large to represent is an error. Assumes the rate stays constant. Not covered: a changing rate, fees, taxes, and the capital limits a venue may set. Use when user asks "how much will I make compounding 0.01% funding for 90 days?" or "what's my APY on this carry position?". Funding received is split by reinvestPct (the rest is withdrawn and still counts as earned); funding paid comes out of capital in full, and the capital never goes below 0. Returns: finalCapital, totalWithdrawn, endValue, totalEarned, totalEarnedPct, annualizedAPY, dailyEarnings, snapshots.

NameTypeReqDescription
durationDaysnumberyesNumber of days to project, up to 3650
fundingRatePctnumberyesFunding rate per interval in PERCENT: 0.01 means 0.01%, so a quoted 0.0125% is 0.0125, never 0.000125
initialCapitalnumberyesStarting capital in USDT
intervalHoursnumber–Hours between funding payments, the period fundingRatePct covers, a whole number of hours that divides 24. Default 8; 1 on Hyperliquid, dYdX, Kraken and Backpack (per-hour rates); 4 or 2 on some symb…
reinvestPctnumber–Percentage of funding received that is reinvested each interval, 0-100 (the rest is withdrawn and counts as earned; funding paid always comes out of capital). 100 = full compounding. Default 100.

No output schema declared.

No examples provided.

workflow.run_covered_call_protective_put ~801

Covered call (long the coin + short a call against it, for yield) or protective put (long the coin + long a put, for downside insurance) on a Deribit BTC/ETH position. Returns the standard annualized-yield metric (premium ÷ 1 coin, annualized by 365/daysToExpiry) up front: that number doesn't depend on any price scenario. Also returns the USD value of the combined position at a given scenario price: covered call caps upside at strike + premium×scenarioPrice (the premium's own coin-denominated value still scales with price, unlike a textbook USD-settled cap); protective put floors value at strike×(1−premium), which is the true minimum across every possible settlement price, not just an approximation. Edge cases: spotEntry, strike, daysToExpiry, quantity and scenarioPrice above zero; premiumCoin above zero and at most 0.999 (Deribit form). The annualized yield is simple, 365 / daysToExpiry, not compounded. Not covered: early assignment, margin, fees, taxes, dividends, rolling, and the P&L before expiry. Use when user asks "what annualized yield do I get selling covered calls on my BTC?" or "how much does insuring my BTC with a put cost me?". Returns: staticYieldPct, annualizedYieldPct, valueAtScenarioUsd, breakevenPrice (covered_call only), floorValueUsd (protective_put only), vsHoldingUsd (vs. just holding the coin). With exchange "binance" (USDT-settled, premiumUsdt) the yield is premium divided by spotEntry (one unit is not a fraction of a coin), annualized by 365/daysToExpiry, and it returns: staticYieldPct, annualizedYieldPct, valueAtScenarioUsdt (covered call = min(S, K) + premium per unit), breakevenPrice (covered_call: spotEntry - premium, null when the cap sits below the cost), capValuePerUnitUsdt (covered_call: strike + premium), floorValuePerUnitUsdt (protective_put: strike - premium), vsHoldingUsdt; USDT is not converted to USD.

NameTypeReqDescription
currencystring–Underlying. Default BTC. XAU and XAG (gold, silver) only with exchange binance.
daysToExpirynumberyesCalendar days until expiry; used to annualize the yield/cost
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 (…
premiumCoinnumber–Deribit only. Premium received (covered_call) or paid (protective_put) per contract, in the base coin
premiumUsdtnumber–Binance only. Premium received (covered_call) or paid (protective_put) per unit, in USDT; must be < spotEntry for a covered call and < strike for a protective put
quantitynumberyesCoin units held / contracts (1:1 covered)
scenarioPricenumberyesUnderlying price in USD to evaluate the combined position's value at
spotEntrynumberyesPrice you acquired/value the underlying coin at, USD; used for the covered-call breakeven vs. cost basis
strategystringyes"covered_call" (hold the coin, sell a call against it) or "protective_put" (hold the coin, buy a put as insurance)
strikenumberyesOption strike, USD

No output schema declared.

No examples provided.

workflow.run_cross_venue_arbitrage ~605

Checks 2-5 quotes for the SAME real-world binary bet across venues (or manually-supplied probabilities) for a direction-independent price gap at the quoted prices: "Yes" at whichever venue quotes it cheapest, "No" at whichever venue quotes "Yes" most expensively (its own "No" price is assumed to be 1 minus its own "Yes" price, the standard complementary-binary convention). Reports isArbitrage, the cost to lock in $1 of guaranteed payout, the locked-in profit and ROI at the quoted prices for a given stake, and which venue quotes each side. feeFractionPerLeg (older name feePctPerLeg, same fraction) is an optional per-leg trading-fee rate that can and does erase a real-looking spread - reported honestly via isArbitrage rather than always showing a positive number. Edge cases: 2 to 5 quotes or 2 to 5 manualProbabilitiesPct (each 0.01 to 99.99); stakeUsd above zero; feeFractionPerLeg 0 to 0.2 as a fraction, 0.01 is 1% (default 0). The No price of a venue is taken as 1 minus its Yes price. A gap that fees erase is reported as isArbitrage false. Not covered: the identifiers being the same bet and resolving the same way (you confirm that), order book depth and slippage, withdrawal and deposit costs, settlement-rule differences, and capital lock-up until resolution. Use when user asks "can I arbitrage this bet across venues?" or "does the quoted price gap survive fees?". The caller asserts the venues quote the same bet; this tool does not verify that. If available is false, do not use any result field (computed figures and any verdict are null or empty), so read available first.

NameTypeReqDescription
feeFractionPerLegnumber–Optional per-leg trading fee as a FRACTION of the price: 0.01 means 1%, 0.001 means 0.1%, 0.02 means 2%; maximum 0.2 (20%). Default 0. Use this field for any fee.
feePctPerLegnumber–Older name of feeFractionPerLeg, kept so existing callers keep working; the value is the same FRACTION, not a percent (0.01 is 1%). Prefer feeFractionPerLeg.
manualProbabilitiesPctarray–Manual mode: 2-5 probabilities (0.01-99.99) already known for the same bet across different venues, when you don't want a live fetch. Provide this OR quotes, not both.
quotesarray–Live mode: one entry per venue, 2-5 total. Provide this OR manualProbabilitiesPct, not both.
stakeUsdnumberyesTotal capital to deploy across both legs

No output schema declared.

No examples provided.

workflow.run_crypto_profit ~533

Profit or loss on a spot crypto trade (coins bought and sold outright, no leverage, no funding) after both fees. Give exactly one of investment (total cash spent, buy fee included) or quantity (coins bought). Each fee is a fraction of that fill's trade value (0.001 = 0.1%): the buy fee is paid on top of the coins' cost, the sell fee comes out of the sale value. For a leveraged perpetual futures position see workflow.run_pnl_planning. Edge cases: buyPrice and sellPrice above zero; give exactly one of investment (above zero, buy fee included) or quantity (above zero); buyFeePct and sellFeePct are fractions from 0 to 0.05 (default 0); holdingDays optional, annualized return only from 30 days. Spot only. Not covered: taxes, withdrawal and network fees, slippage, price moves in the quote currency, and leveraged positions (use workflow.run_pnl_planning). Use when user asks "I bought BTC at $X, what is my profit if I sell at $Y?" or "what price do I need to sell at to break even after fees?". Returns: quantity, totalCost, proceeds, totalFees, profit, roiPct and priceChangePct (fractions), priceMultiple, breakevenSellPrice, annualizedReturnPct (a fraction, only when holdingDays is given and is at least 30, null otherwise: annualizing a shorter hold gives meaningless figures).

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, in the quote currency (e.g. 60000 for BTC in USD)
holdingDaysnumber–Optional: days the coins were held; 30 or more also returns the annualized return
investmentnumber–Total cash spent on the buy, buy fee included (e.g. 1000). Give this or quantity, not both
quantitynumber–Number of coins bought (e.g. 0.5). Give this or investment, not both
sellFeePctnumber–Sell fee as a fraction of the trade value, 0 to 0.05 (0.001 = 0.1%). Default 0
sellPricenumberyesPrice per coin at the sale, or the price to test, same currency

No output schema declared.

No examples provided.

workflow.run_dca_entry ~411

DCA entry planner: weighted average entry price, breakeven, and per-level contribution from multiple fill prices and sizes. Each fill is { price, size } here (primitive.average_entry calls the same field quantity). Compared with primitive.average_entry, this one adds output for the case where breakeven or the per-level breakdown is also wanted, not just the bare average. Edge cases: 2 to 20 fills (size also accepted as quantity), each price and size above zero; fee_open_pct and fee_close_pct are fractions from 0 to 0.05 (defaults 0.0002 and 0.0005); every fill is on the same side and the same contract type. Not covered: fills at different times with different fees, partial closes, funding paid while the position was open, and liquidation (use workflow.run_liquidation_safety). Use when user bought at several prices and asks "what's my average entry?" or "where is my DCA breakeven?". Returns: averageEntry, breakeven, per-level summary.

NameTypeReqDescription
contractTypestring–linear = USDT-margined (default), inverse = coin-margined. Each fill's size is USD notional (contracts) for inverse; averageEntry is then the harmonic mean of fill prices, not the arithmetic mean.
entriesarrayyesFills to average (2 to 20). Each: { price, size }, e.g. [{ "price": 60000, "size": 0.5 }, { "price": 58000, "size": 1 }]. Size is base-asset quantity for linear, USD notional (contracts) for inverse.
fee_close_pctnumber–Close fee rate (default 0.0005)
fee_open_pctnumber–Open fee rate (default 0.0002)
sidestringyesTrade direction: "long" or "short"

No output schema declared.

No examples provided.

workflow.run_dsr ~698

Deflated Sharpe Ratio (Bailey & Lopez de Prado): given how many strategy variants you tried (and how correlated they are), what Sharpe ratio would the *best of N* clear by luck alone, and does your actual strategy still clear that higher bar? Edge cases: returns at least 3; give either trial_sharpes (at least 2 values, per period; identical values are an error) or n_trials (a whole number from 2 to 1e9); avg_correlation 0 to below 1 (default 0) works only with n_trials; null_mean works only with trial_sharpes; an effective trial count of 1 or less is an error. Not covered: the real number of trials you ran if you do not state it (the result is only as honest as n_trials), multiple testing across strategies you did not count, and out-of-sample proof. Use when user asks "is my backtested Sharpe ratio real, or did I get lucky trying many variants?" or "how many independent trials does this really represent?". Provide either trial_sharpes[] (the N trials' own observed Sharpe ratios, most rigorous) or n_trials (+ optional avg_correlation to correct for correlated trials via Kish's design effect). Two limits to know. n_trials assumes the paper's illustrative case (trial Sharpes with mean 0 and variance 1, in per-period units), which is a very high bar for a low-frequency series: the threshold is about 1.6 at N=10, 2.5 at N=100 and 3.3 at N=1000, while a daily series has a per-period Sharpe of order 0.05, so dsr comes out effectively 0; use trial_sharpes there. trial_sharpes centers the threshold on the trials' own mean Sharpe plus their dispersion times the expected-maximum factor; this answers "does my strategy beat the best of N trials drawn from the spread I observed", not the zero-skill-null variant; pass null_mean true for that variant (mean fixed at 0, spread still taken from the trials); the two thresholds differ by exactly the trials' mean Sharpe. Returns: expected_max_sharpe (the luck-alone threshold), dsr (probability your strategy's true Sharpe exceeds it, 0-1…

NameTypeReqDescription
avg_correlationnumber–Average pairwise correlation between trials, 0-1 (default 0 = independent). Only used with n_trials; lowers the effective trial count via Kish's design effect.
n_trialsnumber–Number of strategy variants tried, if trial_sharpes were not tracked individually. Assumes trial Sharpes with mean 0 and variance 1 (per-period units): too strict for daily series, prefer trial_sharp…
null_meanboolean–Only used with trial_sharpes. true = centre the luck threshold on 0 (zero-skill null) instead of on the trials' own mean Sharpe; the spread still comes from the trials. Default false.
returnsarrayyesThe candidate strategy's own return series
trial_sharpesarray–Observed Sharpe ratios of all N trials tried, if tracked. Takes priority over n_trials if both are given.

No output schema declared.

No examples provided.

workflow.run_event_study ~663

Event study with a placebo: is the average return after your events (a listing, an unlock, a signal firing) different from the average return of the same window started on random non-event dates? Give event_returns and placebo_returns in the same units; optional event_tickers and placebo_tickers (one per return) cluster the standard error by ticker, because events on one coin are not independent draws. Returns the effect (event mean minus placebo mean), Welch t-test, permutation p-value (exact when the number of splits is small, otherwise seeded random shuffles; two-sided as scipy.stats.permutation_test defines it), the cluster-robust t and p (statsmodels cluster covariance, t with clusters-1 degrees of freedom), the single event carrying most of the effect with the effect once it is dropped, honesty flags (few events, few clusters, one event dominates, sign flips without it, clustering changes the verdict) and a verdict that is distinguishable_from_placebo, not_distinguishable or fragile. It tests a difference you hand it; it does not pick dates, fetch prices or correct for look-ahead. Edge cases: event_returns and placebo_returns each 2 to 5000 finite values; event_tickers and placebo_tickers, if given, one per return, 1 to 32 characters; n_permutations a whole number 1000 to 100,000 (default 10,000) and permutations times events at most 50,000,000; alpha strictly between 0 and 0.5 (default 0.05); seed a whole number (same seed, same result); two constant samples are an error. Not covered: choosing the event window or the placebo set (the result is only as good as that choice), overlapping events, clustering in time, and causality. Use when user asks "is this effect real or noise", "does my signal beat random dates" or "run an event study with a placebo". Without at least two ticker clusters the verdict is never distinguishable_from_placebo, because there is no clustered test to confirm it.

NameTypeReqDescription
alphanumber–Significance level for the verdict, above 0 and below 0.5. Default 0.05.
event_returnsarrayyesOne return per event over the event window, any consistent unit (percent or fraction). 2 to 5000 values.
event_tickersarray–Optional, one ticker per event return, used to cluster. Omitted: every event is its own cluster.
n_permutationsinteger–Random shuffles when the exact test is too large, 1000 to 100000. Default 10000.
placebo_returnsarrayyesReturns over a window of the same length started on random dates without an event. 2 to 5000 values; event and placebo together at most 5000.
placebo_tickersarray–Optional, one ticker per placebo return. Omitted: every placebo is its own cluster.
seedinteger–Seed for the shuffles, 0 to 4294967295; same input and seed give the same result. Default 1.

No output schema declared.

No examples provided.

workflow.run_evt_tail_risk ~527

Extreme Value Theory tail risk (Peaks-Over-Threshold): fits a Generalized Pareto Distribution to the losses beyond a high threshold via Grimshaw's (1993) profile-likelihood MLE, then extrapolates VaR/Expected Shortfall at the requested confidence, without assuming a normal distribution. Edge cases: at least 100 finite returns; threshold_percentile strictly between 0 and 100 (default 90); confidence strictly between 0 and 1 (default 0.99); at least 10 returns beyond the threshold, otherwise an error; if the tail fit does not converge, the call is an error suggesting another threshold. Not covered: a tail model for gains, time-varying volatility, the choice of the best threshold (try several), and the risk beyond what the sample has seen. Use when user asks "what's my tail VaR without assuming normality?" or "how fat is my loss tail, really?". Complements workflow.run_var_cvar (parametric, normal-distribution VaR/CVaR) for exactly the fat-tailed-return case that assumption understates. threshold_percentile (default 90) sets which percentile of the loss distribution (losses = -returns) becomes the threshold u; confidence must be deep enough into the fitted tail (1-confidence < the threshold's own exceedance rate) or the call throws. Returns: threshold, n_exceedances, exceedance_rate, xi (GPD shape: 0=exponential tail, >0=heavy/fat tail, <0=bounded tail; values <= -1 are excluded from the fit domain as a known non-regular/unbounded-likelihood case, Smith 1985), beta (GPD scale), xi_asymptotically_normal (false when xi<=-0.5: the fit is still valid but the usual MLE confidence-interval theory doesn't apply, per that same Smith 1985 result), var, es (null when xi>=1, where Expected Shortfall is mathematically undefined).

NameTypeReqDescription
confidencenumber–VaR/ES confidence level, 0-1 exclusive. Default 0.99. Must satisfy 1-confidence < the threshold's own exceedance rate.
returnsarrayyesReturn series, one value per period, at least 100 values (POT needs real sample depth in the tail)
threshold_percentilenumber–Percentile (0-100 exclusive) of the loss distribution used as the POT threshold u. Default 90.

No output schema declared.

No examples provided.

workflow.run_exit_target ~316

Calculate the exact exit price needed to hit a target PnL or ROE percentage. Edge cases: entryPrice, leverage and sizeBase above zero; targetMode pnl or roe, targetValue any number; fees 0 to 0.05 (defaults 0.0002 and 0.0005); a target that cannot be reached from this position is an error. Not covered: funding, slippage, liquidation before the target, and the chance that price gets there. Use when user asks "at what price do I take profit to make $500?" or "where should I set TP for 20% ROE?". Returns: targetExitPrice.

NameTypeReqDescription
contractTypestring–linear = USDT-margined (default), inverse = coin-margined. For inverse, pnl-mode targetValue and outputs are in the base coin.
entryPricenumberyesEntry price
feeClosePctnumber–Closing fee fraction, default 0.0005
feeOpenPctnumber–Opening fee fraction, default 0.0002
leveragenumberyesLeverage multiplier
sidestringyesTrade direction: "long" or "short"
sizeBasenumberyesPosition size in base asset
targetModestringyes"pnl" = target in USDT, "roe" = target in %
targetValuenumberyesTarget value (USDT/coin for pnl mode, or %)

No output schema declared.

No examples provided.

workflow.run_fibonacci_levels ~301

Fibonacci retracement and extension price levels from a swing high and low, for any asset (forex, stocks, crypto): retracement 0, 23.6, 38.2, 50, 61.8, 78.6 and 100 percent and extension 127.2, 161.8, 200 and 261.8 percent, as prices. direction "up" measures a rise from the low to the high, "down" a fall from the high to the low; 0 percent is the end of the swing and 100 percent its start. A level at or below zero (an extension of a steep fall) comes back as price null. The ratios are a charting convention, not a forecast. Pure price arithmetic, no pair or market data. Edge cases: high and low above zero and finite, high above low (equal or reversed is an error); direction is up or down. Not covered: choosing the swing points, confluence with other levels, and any statement about where price will turn; the levels are arithmetic.

NameTypeReqDescription
directionstringyes"up": the swing rose from the low to the high; "down": it fell from the high to the low
highnumberyesSwing high price (positive, above the low, at most 1e300)
lownumberyesSwing low price (positive, below the high)

No output schema declared.

No examples provided.

workflow.run_forex_average_entry ~176

Size-weighted (arithmetic) average entry price across multiple forex fills. Edge cases: at least 1 fill; every price and units above zero; pair is BASE/QUOTE with two different ISO 4217 codes (a metal such as XAU/USD is accepted here because no pip is needed). The average is weighted by units, not by cash. Not covered: swap, commission, spread, fills in different pairs, and closing fills (buys only). Use when user asks "what's my average entry after these fills?". Returns: totalUnits, totalCost, avgEntry.

NameTypeReqDescription
fillsarrayyesFills to average, each with a price and a size in base-currency units
pairstringyesCurrency pair in BASE/QUOTE format, e.g. "EUR/USD"

No output schema declared.

No examples provided.

workflow.run_forex_breakeven ~413

Breakeven price for a forex position accounting for spread and round-trip commission, in pips and in price. Commission is quoted per standard lot (100,000 units) and expressed in the pair's own quote currency; because both commission and pip value scale with lot size, the commission-in-pips figure is independent of position size by construction. Precious-metal pairs (XAU, XAG, XPT, XPD) are refused with an error, because their pip and lot size differ by broker. Edge cases: entryPrice above zero; spreadPips and commissionPerLotRoundTrip zero or more (commission default 0, in the quote currency per 100,000 units round trip); The pair is BASE/QUOTE with two different ISO 4217 currency codes, in any letter case; crypto tickers and precious metals (XAU, XAG, XPT, XPD) are refused. A pip is 0.01 for a pair quoted in JPY and 0.0001 for every other pair, and a standard lot is 100,000 units. Not covered: swap, slippage, requotes, account-currency conversion, and a commission quoted per side or per million. Use when user asks "where's my true breakeven after spread and commission?". Returns: pipSize, commissionPips, totalCostPips, breakevenPrice.

NameTypeReqDescription
commissionPerLotRoundTripnumber–Round-trip commission per standard lot, in the pair's own quote currency. Default 0 (pure-spread broker model).
entryPricenumberyesEntry price in the pair's own quote terms, e.g. 1.0850 for EUR/USD
pairstringyesCurrency pair in BASE/QUOTE format, e.g. "EUR/USD"
sidestringyesTrade direction: "long" or "short"
spreadPipsnumberyesSpread at entry, in pips

No output schema declared.

No examples provided.

workflow.run_forex_correlation ~289

Correlation coefficient and minimum-variance hedge ratio between two price series of matching length, computed on daily % returns (not raw price levels, which would give spuriously high correlation between two unrelated but both-trending series). hedgeRatio follows Hull's standard futures-hedging formula: cov(returns1,returns2)/var(returns2), "how many units of series 2 per unit of series 1 minimizes the combined position's variance." No live data fetch: supply the two price series directly. The live variant is workflow.run_forex_correlation_live, which has both series fetched automatically for two named pairs. Edge cases: each series needs at least 5 positive prices, and both series must be the same length with one price per matching date (a different length is an error); a series with no movement (zero return variance) is an error because correlation is undefined. Not covered: lagged correlation, rolling windows, significance tests and confidence intervals; 4 returns is the mathematical minimum, not a reliable sample. Use when user already has two price series and wants their statistical relationship. Returns: n, correlation (-1 to 1), hedgeRatio.

NameTypeReqDescription
rates1arrayyesFirst price series, chronological order, one price per date
rates2arrayyesSecond price series, chronological order, same length and same dates as rates1

No output schema declared.

No examples provided.

workflow.run_forex_correlation_live ~364

Correlation coefficient and minimum-variance hedge ratio between two forex pairs, fetched live: historical daily rates for both pairs over the given lookback window (frankfurter.app's daily ECB reference time series, business days only), aligned by matching date, computed on daily % returns. hedgeRatio follows Hull's standard futures-hedging formula: "how many units of pair2 per unit of pair1 minimizes the combined position's variance." Edge cases: days is a whole number from 14 to 365 (default 30) of calendar days, so fewer trading days are used; both pairs must be BASE/QUOTE of two different ISO 4217 codes; dates present in only one series are dropped; too few overlapping dates, or a flat series, gives available false. Daily ECB reference rates only, no intraday data. Not covered: lagged correlation, rolling windows and significance tests. Use when user asks "how correlated are EUR/USD and GBP/USD?" or "what hedge ratio should I use between these two pairs?". Returns: n (overlapping trading days used), correlation (-1 to 1), hedgeRatio, available (false + error if either pair has no data, or too few dates overlap). If available is false, do not use any result field (computed figures and any verdict are null or empty), so read available first.

NameTypeReqDescription
daysinteger–Calendar days to look back, 14-365. Default 30. Business-day-only data means fewer actual points than this number.
pair1stringyesFirst currency pair in BASE/QUOTE format, e.g. "EUR/USD"
pair2stringyesSecond currency pair in BASE/QUOTE format, e.g. "GBP/USD"

No output schema declared.

No examples provided.

workflow.run_forex_currency_converter ~172

Converts an amount between currencies using a manually supplied rate: no live data fetch. The live variant is workflow.run_forex_currency_converter_live, which has the rate fetched automatically. Edge cases: rate above zero; amount may be zero or negative (it is converted as given); the tool takes the amount and the rate only, no currency codes. Not covered: bank or broker markups, fees, rounding rules of a particular provider, and the direction of the rate (you must supply the rate that applies from the first to the second currency). Use when user already knows the exact rate they want applied. Returns: converted.

NameTypeReqDescription
amountnumberyesAmount in the source currency
ratenumberyesExchange rate to apply (1 unit of source currency = rate units of target currency)

No output schema declared.

No examples provided.

workflow.run_forex_currency_converter_live ~280

Converts an amount between currencies using a live FX rate: TrueFX for its 10 quoted majors (genuinely live tick data), frankfurter.app daily ECB reference rate as the fallback for every other currency pair (30 total). Edge cases: amount may be zero or negative (converted as given); from and to are ISO 4217 codes; the same currency on both sides returns the amount with source identity; no rate found gives available false and no figure. The rate is a TrueFX tick or a daily ECB reference rate, not what a bank or broker would give you. Not covered: markups, fees and rounding rules of a provider. Use when user asks "what's $X worth in EUR?" or any currency conversion where the rate itself isn't already known. Returns: converted, rate, source (truefx/frankfurter/identity), asOf, available (false + error if no rate could be found for that pair). If available is false, do not use any result field (computed figures and any verdict are null or empty), so read available first.

NameTypeReqDescription
amountnumberyesAmount in the source currency
fromstringyes3-letter source currency code, e.g. "USD"
tostringyes3-letter target currency code, e.g. "EUR"

No output schema declared.

No examples provided.

workflow.run_forex_margin_level ~205

Free margin and margin level % from account equity and used margin: equity/usedMargin*100, the same stop-out proximity metric every forex platform shows. Returns null (not Infinity) when usedMargin is 0, meaning no open position. Edge cases: equity above zero, usedMargin zero or more; usedMargin of 0 returns marginLevelPct null (no open position), not a large number; equity below used margin gives a level under 100. Not covered: a broker margin-call or stop-out threshold (they differ by broker), pending orders, hedged-position margin offsets, and swap or commission not yet charged. Use when user asks "how close am I to a margin call?" or "what's my free margin?". Returns: freeMargin, marginLevelPct.

NameTypeReqDescription
equitynumberyesAccount equity (balance + floating P&L)
usedMarginnumberyesMargin currently locked by open positions. 0 if none.

No output schema declared.

No examples provided.

workflow.run_forex_margin_required ~256

Notional and margin required for a forex position, in the pair's own quote currency: no live FX rate needed. The live variant is workflow.run_forex_margin_required_live, which applies when the account currency differs from the pair's quote currency. Edge cases: units, price and leverage above zero (leverage 50 means 50:1); the pair is BASE/QUOTE with two different ISO 4217 codes (no pip is needed, so a metal pair is accepted). Margin is notional / leverage in the quote currency. Not covered: broker margin tiers, per-instrument leverage caps, hedge offsets, and conversion to the account currency (use workflow.run_forex_margin_required_live). Use when user asks "how much margin do I need for X lots of EUR/USD at 50:1?". Returns: notionalQuote, marginQuote, base, quote.

NameTypeReqDescription
leveragenumberyesLeverage multiplier, e.g. 50 for 50:1
pairstringyesCurrency pair in BASE/QUOTE format, e.g. "EUR/USD"
pricenumberyesEntry or current price
unitsnumberyesPosition size in base-currency units

No output schema declared.

No examples provided.

workflow.run_forex_margin_required_live ~301

Notional and margin required for a forex position, converted to a given account currency via a live FX rate (same TrueFX/frankfurter.app source as workflow.run_forex_pip_value_live). Edge cases: same input rules as workflow.run_forex_margin_required; when no rate is found for the account currency, available is false and no figure is returned. The rate is a TrueFX tick or a daily ECB reference rate, not a dealer quote. Not covered: broker margin tiers and margin offsets on hedged positions. Use when user asks "how much margin do I need in my account currency?" and the account currency differs from the pair's own quote currency. Returns everything workflow.run_forex_margin_required does, plus accountCurrency, notionalAccount, marginAccount, fxRate, fxSource, available (false + error if no rate could be found). If available is false, do not use any result field (computed figures and any verdict are null or empty), so read available first.

NameTypeReqDescription
accountCurrencystringyes3-letter account currency code, e.g. "GBP"
leveragenumberyesLeverage multiplier, e.g. 50 for 50:1
pairstringyesCurrency pair in BASE/QUOTE format, e.g. "EUR/USD"
pricenumberyesEntry or current price
unitsnumberyesPosition size in base-currency units

No output schema declared.

No examples provided.

workflow.run_forex_pip_value ~405

Value of 1 pip for a given forex pair and position size, in that pair's own quote currency (e.g. EUR/USD's pip value comes back in USD, USD/JPY's in JPY): no live FX rate needed, since a pair's pip value is naturally denominated in its own quote currency. Pip size is 0.0001 for non-JPY pairs, 0.01 for JPY-quoted pairs, a universal market convention verified against real broker documentation, not broker-specific. The live variant is workflow.run_forex_pip_value_live, which applies when the account currency differs from the pair's quote currency. Precious-metal pairs (XAU, XAG, XPT, XPD) are refused with an error, because their pip and lot size differ by broker. Edge cases: units above zero; The pair is BASE/QUOTE with two different ISO 4217 currency codes, in any letter case; crypto tickers and precious metals (XAU, XAG, XPT, XPD) are refused. A pip is 0.01 for a pair quoted in JPY and 0.0001 for every other pair, and a standard lot is 100,000 units. The value comes back in the pair quote currency. Not covered: brokers that use a fractional pip (pipette), non-standard lot sizes, metals and indices, and the account-currency conversion (use workflow.run_forex_pip_value_live). Use when user asks "what's 1 pip worth on X lots of EUR/USD?". Returns: pipSize, pipValueQuote, base, quote.

NameTypeReqDescription
pairstringyesCurrency pair in BASE/QUOTE format, e.g. "EUR/USD"
unitsnumberyesPosition size in base-currency units (1 standard lot = 100,000, mini = 10,000, micro = 1,000, nano = 100)

No output schema declared.

No examples provided.

workflow.run_forex_pip_value_live ~348

Value of 1 pip for a forex pair and position size, converted to a given account currency via a live FX rate: TrueFX for its 10 quoted majors (genuinely live tick data), frankfurter.app daily ECB reference rate as the fallback for every other currency (30 total). Precious-metal pairs (XAU, XAG, XPT, XPD) are refused with an error, because their pip and lot size differ by broker. Edge cases: same input rules as workflow.run_forex_pip_value; when no rate is found for the account currency, available is false and no figure is returned. The rate is a TrueFX tick or a daily ECB reference rate, not a dealer quote. Not covered: broker markups and fractional pips. Use when user asks "what's 1 pip worth in my account currency?" and the account currency differs from the pair's own quote currency (if it matches, workflow.run_forex_pip_value alone is enough, no live fetch needed). Returns everything workflow.run_forex_pip_value does, plus accountCurrency, pipValueAccount, fxRate, fxSource (truefx/frankfurter/identity), available (false + error if no rate could be found for that currency). If available is false, do not use any result field (computed figures and any verdict are null or empty), so read available first.

NameTypeReqDescription
accountCurrencystringyes3-letter account currency code, e.g. "GBP"
pairstringyesCurrency pair in BASE/QUOTE format, e.g. "EUR/USD"
unitsnumberyesPosition size in base-currency units

No output schema declared.

No examples provided.

workflow.run_forex_pnl ~339

Profit or loss for a closed or hypothetical forex trade, in pips and in the pair's own quote currency, long or short. Precious-metal pairs (XAU, XAG, XPT, XPD) are refused with an error, because their pip and lot size differ by broker. Edge cases: entryPrice, exitPrice and units above zero; The pair is BASE/QUOTE with two different ISO 4217 currency codes, in any letter case; crypto tickers and precious metals (XAU, XAG, XPT, XPD) are refused. A pip is 0.01 for a pair quoted in JPY and 0.0001 for every other pair, and a standard lot is 100,000 units. The result is in the quote currency; a short position gains when the price falls. Not covered: spread, commission, swap, slippage and account-currency conversion. Use when user asks "what did I make/lose on this trade?" or "what would X pips be worth on Y lots?". Returns: pips (signed, positive favors the position taken), pnlQuote.

NameTypeReqDescription
entryPricenumberyesEntry price in the pair's own quote terms, e.g. 1.0850 for EUR/USD
exitPricenumberyesExit price, same quote convention as the entry price
pairstringyesCurrency pair in BASE/QUOTE format, e.g. "EUR/USD"
sidestringyesTrade direction: "long" or "short"
unitsnumberyesPosition size in base-currency units

No output schema declared.

No examples provided.

workflow.run_forex_position_size_live ~469

Position size (units and standard lots) from a risk amount and stop distance, in a given account currency, via a live FX rate to convert pip value into that currency (same TrueFX/frankfurter.app source as the other forex _live tools). Never has a meaningful account-currency-agnostic form: sizing a position from a risk budget genuinely requires knowing what 1 pip is worth in the currency that budget is denominated in. Precious-metal pairs (XAU, XAG, XPT, XPD) are refused with an error, because their pip and lot size differ by broker. Edge cases: entryPrice, stopPrice and riskAmount above zero; a stop equal to the entry gives available false (no risk distance); The pair is BASE/QUOTE with two different ISO 4217 currency codes, in any letter case; crypto tickers and precious metals (XAU, XAG, XPT, XPD) are refused. A pip is 0.01 for a pair quoted in JPY and 0.0001 for every other pair, and a standard lot is 100,000 units. Units are not rounded to a broker lot step. Not covered: spread and slippage on the stop, commission, margin limits, and a minimum or step lot size of your broker. Use when user asks "how many lots should I trade to risk $X on this setup?". Returns: stopDistancePips, units, lots, pipValuePerUnitAccount, fxRate, fxSource, available (false + error if entry equals stop, or if no rate could be found). If available is false, do not use any result field (computed figures and any verdict are null or empty), so read available first.

NameTypeReqDescription
accountCurrencystringyes3-letter account currency code, e.g. "USD"
entryPricenumberyesEntry price in the pair's own quote terms, e.g. 1.0850 for EUR/USD
pairstringyesCurrency pair in BASE/QUOTE format, e.g. "EUR/USD"
riskAmountnumberyesAmount to risk, in accountCurrency
stopPricenumberyesStop-loss price, same quote convention as the entry price

No output schema declared.

No examples provided.

workflow.run_forex_risk_reward ~409

Risk and reward distance in pips from entry/stop/target, and the resulting ratio (reward/risk): a raw number, not a verdict. ratio is null when the stop sits exactly at entry (no risk distance), and also when validSetup is false (stop/target on the wrong side of entry for the given side, e.g. a long with its stop above entry) - check validSetup before trusting the ratio. Precious-metal pairs (XAU, XAG, XPT, XPD) are refused with an error, because their pip and lot size differ by broker. Edge cases: entryPrice, stopPrice and targetPrice above zero; The pair is BASE/QUOTE with two different ISO 4217 currency codes, in any letter case; crypto tickers and precious metals (XAU, XAG, XPT, XPD) are refused. A pip is 0.01 for a pair quoted in JPY and 0.0001 for every other pair, and a standard lot is 100,000 units. A stop equal to entry or a stop or target on the wrong side of entry for the chosen side gives ratio null (check validSetup). Not covered: spread, commission, swap, slippage, and the probability that the target is hit. Use when user asks "what's my risk/reward on this setup?". Returns: riskPips, rewardPips, validSetup, ratio.

NameTypeReqDescription
entryPricenumberyesEntry price in the pair's own quote terms, e.g. 1.0850 for EUR/USD
pairstringyesCurrency pair in BASE/QUOTE format, e.g. "EUR/USD"
sidestringyesTrade direction: "long" or "short"
stopPricenumberyesStop-loss price, same quote convention as the entry price
targetPricenumberyesTake-profit price, same quote convention as the entry price

No output schema declared.

No examples provided.

workflow.run_forex_scenario ~376

PnL across a range of hypothetical price moves (in pips, signed by actual price direction, not pre-adjusted for side), for a single forex position size, long or short. Precious-metal pairs (XAU, XAG, XPT, XPD) are refused with an error, because their pip and lot size differ by broker. Edge cases: entryPrice and units above zero; deltasPips is a list of at least one signed number of pips (positive means the price rose, whatever the side); a move that takes the exit price to zero or below is not rejected, read exitPrice; The pair is BASE/QUOTE with two different ISO 4217 currency codes, in any letter case; crypto tickers and precious metals (XAU, XAG, XPT, XPD) are refused. A pip is 0.01 for a pair quoted in JPY and 0.0001 for every other pair, and a standard lot is 100,000 units. Not covered: spread, commission, swap, slippage and account-currency conversion. Use when user asks "what if price moves X pips in either direction?". Returns: scenarios[] (deltaPips, exitPrice, pnlQuote).

NameTypeReqDescription
deltasPipsarrayyesHypothetical price moves in pips, e.g. [-50, 0, 50]
entryPricenumberyesEntry price in the pair's own quote terms, e.g. 1.0850 for EUR/USD
pairstringyesCurrency pair in BASE/QUOTE format, e.g. "EUR/USD"
sidestringyesTrade direction: "long" or "short"
unitsnumberyesPosition size in base-currency units

No output schema declared.

No examples provided.

workflow.run_forex_swap_cost ~416

Total swap/rollover cost (or credit) for holding a forex position overnight, in the pair's own quote currency: no live FX rate needed. Swap rates are broker-set with no free live feed available, so swapPerLotPerNight is always a manual input (quoted per standard lot, matching how commission is quoted in workflow.run_forex_breakeven), not fetched. Negative = cost (you pay), positive = credit (you receive). The live variant is workflow.run_forex_swap_cost_live, which applies when the account currency differs from the pair's quote currency. Precious-metal pairs (XAU, XAG, XPT, XPD) are refused with an error, because their pip and lot size differ by broker. Edge cases: units above zero; nights a whole number above zero; swapPerLotPerNight any number, negative is a cost, positive a credit, quoted per 100,000 units in the quote currency; The pair is BASE/QUOTE with two different ISO 4217 currency codes, in any letter case; crypto tickers and precious metals (XAU, XAG, XPT, XPD) are refused. Not covered: the triple swap on Wednesday (count it in nights yourself), changing swap rates, and account-currency conversion (use workflow.run_forex_swap_cost_live). Use when user asks "how much will holding this position overnight cost me?". Returns: lots, totalSwapQuote, base, quote.

NameTypeReqDescription
nightsintegeryesNumber of nights the position is held
pairstringyesCurrency pair in BASE/QUOTE format, e.g. "EUR/USD"
swapPerLotPerNightnumberyesSwap rate per standard lot (100,000 units) per night, in the pair's quote currency. Negative = cost, positive = credit. Broker-set: get this from the user's broker platform, there is no live source f…
unitsnumberyesPosition size in base-currency units

No output schema declared.

No examples provided.

workflow.run_forex_swap_cost_live ~372

Total swap/rollover cost (or credit) for holding a forex position overnight, converted to a given account currency via a live FX rate (same TrueFX/frankfurter.app source as the other forex _live tools). swapPerLotPerNight is still always a manual input: swap rates are broker-set, with no free live feed available for them. Precious-metal pairs (XAU, XAG, XPT, XPD) are refused with an error, because their pip and lot size differ by broker. Edge cases: same input rules as workflow.run_forex_swap_cost (nights a whole number, swap any sign); when no rate is found for the account currency, available is false and no figure is returned. Not covered: the triple swap on Wednesday and swap rates that change during the hold. Use when user asks "how much will holding this position overnight cost me in my account currency?" and it differs from the pair's own quote currency. Returns everything workflow.run_forex_swap_cost does, plus accountCurrency, totalSwapAccount, fxRate, fxSource, available (false + error if no rate could be found). If available is false, do not use any result field (computed figures and any verdict are null or empty), so read available first.

NameTypeReqDescription
accountCurrencystringyes3-letter account currency code, e.g. "GBP"
nightsintegeryesNumber of nights the position is held
pairstringyesCurrency pair in BASE/QUOTE format, e.g. "EUR/USD"
swapPerLotPerNightnumberyesSwap rate per standard lot per night, in the pair's quote currency. Negative = cost, positive = credit.
unitsnumberyesPosition size in base-currency units

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.