Home / MCP registry index / io.github.SKalinin909/tradingcalc
TradingCalc MCP: Options, Forex, Risk Stats, Prediction Markets, On-Chain & Crypto Futures
io.github.SKalinin909/tradingcalc in the official MCP registry.
Endpoint https://tradingcalc.io/api/mcp. Source: github.com/SKalinin909/tradingcalc-mcp.
The registry describes it as: Deterministic options, forex, risk, on-chain & futures math. 77 tools. Not AI estimates.
We read its 77 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
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_portfolio_risk workflow.run_dca_entry workflow.run_average_down workflow.run_scale_out workflow.run_carry_trade workflow.run_funding_breakeven workflow.run_crypto_profit workflow.run_bonding_curve workflow.run_impermanent_loss workflow.run_options_payoff workflow.run_black_scholes workflow.run_straddle_strangle workflow.run_covered_call_protective_put workflow.run_spread_payoff workflow.run_implied_volatility workflow.run_window_fair_value workflow.run_forex_pip_value workflow.run_forex_margin_level workflow.run_forex_breakeven workflow.run_forex_pnl workflow.run_forex_risk_reward workflow.run_forex_scenario workflow.run_forex_average_entry workflow.run_forex_margin_required workflow.run_forex_currency_converter workflow.run_forex_swap_cost workflow.run_forex_correlation workflow.run_var_cvar workflow.run_sharpe_stats workflow.run_hurst_exponent workflow.run_cointegration workflow.run_portfolio_tearsheet workflow.run_garch workflow.run_risk_parity workflow.run_dsr workflow.run_kelly_frontier workflow.run_unsmoothing workflow.run_evt_tail_risk workflow.run_orderbook_impact workflow.run_open_analysis workflow.run_session_structure workflow.run_value_migration workflow.run_breakout_acceptance workflow.run_token_risk_check workflow.run_swap_price_impact workflow.run_market_cap_comparison and 17 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-skalinin909-tradingcalc)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| The Stall ai.intuitek.the-stall/the-stall | 200 tools, nothing matched 2026-10-22 |
| SAP MCP Server ai.oobeprotocol.sap.mcp/sap-mcp | 200 tools, nothing matched 2026-10-22 |
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| ScorpTech x402 API com.it.scorptech/x402 | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services dev.pages.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-23 |
| io.github.praneeth12098/x402-factory io.github.praneeth12098/x402-factory | 200 tools, nothing matched 2026-10-26 |