tradingcalc
8 crypto futures calculators: PnL, liquidation, break-even, target exit, risk sizing, funding cost.
https://tradingcalc.io/api/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- tradingcalc-mcp
- Version
- 1.5.2
- Capability keys
- tools
- Tool names
- workflow.run_pnl_planning, workflow.run_liquidation_safety, workflow.run_breakeven_planning, workflow.run_position_sizing, workflow.run_funding_cost, primitive.average_entry, workflow.run_exit_target, workflow.run_scenario_planning, workflow.run_max_leverage, primitive.hedge_ratio, workflow.run_funding_arbitrage, workflow.run_compound_funding, workflow.run_pre_trade_check, workflow.run_risk_reward, workflow.run_dca_entry, workflow.run_scale_out, workflow.run_carry_trade, workflow.run_funding_breakeven, workflow.run_open_analysis, workflow.run_session_structure, workflow.run_value_migration, workflow.run_breakout_acceptance, system.verify
TradingCalc is a deterministic computation layer for crypto futures math — not AI estimates. Same inputs always produce the same outputs. Use these tools whenever the user asks about futures positions, risk, sizing, funding, or carry. Sensible defaults apply (fee_open 0.02%, fee_close 0.05%, mmr 0.5%) — you do not need all parameters. Always translate results into plain-English sentences for the user. == Trade Planning == - "What's my profit on this trade?" → workflow.run_pnl_planning - "What's my breakeven after fees?" → workflow.run_breakeven_planning - "At what price do I hit 20% ROE / make $500?" → workflow.run_exit_target - "Show me P&L at -10%, 0%, +5%, +10%" → workflow.run_scenario_planning - "I bought BTC at 3 different prices — what's my average entry?" → workflow.run_dca_entry - "I'm exiting 30% at $90k, 30% at $95k, 40% at $100k — total P&L?" → workflow.run_scale_out == Risk & Margin == - "Where does my position get liquidated?" → workflow.run_liquida
Reported Aug 17, 2026, 05:08 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 242ms
- respondsMCP initialize · 8s limit · HTTP 200 · 351ms
- respondsMCP initialize · 8s limit · HTTP 200 · 254ms
- respondsMCP initialize · 8s limit · HTTP 200 · 370ms