Should my agent depend on the MCP server io.github.SKalinin909/tradingcalc?

Verdict: allow — stale-mid-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

TradingCalc MCP — Crypto Futures Math

io.github.SKalinin909/tradingcalc

Crypto futures math: PnL, liquidation, position sizing, carry trade. 19 tools. Not AI estimates.

— the operator's own registry description reported

Publisher io.github.SKalinin909 · first seen 2026-08-12 · endpoint https://tradingcalc.io/api/mcp

allow

verdict

stale-mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — stale-mid-solo — safe to depend on

Cluster stale-mid-solo · distinctiveness 0.183 (typical). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency241 ms

vs populationtypical

protocolstale

authopen

Use — can it use it?

tools23

vs populationmid

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_ede859d73c55826f0bf8a84d · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

primitive.average_entry primitive.hedge_ratio system.verify workflow.run_breakeven_planning workflow.run_breakout_acceptance workflow.run_carry_trade workflow.run_compound_funding workflow.run_dca_entry workflow.run_exit_target workflow.run_funding_arbitrage workflow.run_funding_breakeven workflow.run_funding_cost workflow.run_liquidation_safety workflow.run_max_leverage workflow.run_open_analysis workflow.run_pnl_planning workflow.run_position_sizing workflow.run_pre_trade_check workflow.run_risk_reward workflow.run_scale_out workflow.run_scenario_planning workflow.run_session_structure workflow.run_value_migration

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	23/23	✓
has a description	23/23	✓
description is substantive	23/23	✓
parameters are typed	23/23	✓
parameters are described	11/23	11/23

23 of 23 tools graded · 23 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2024-11-05

protocol version

—

session model

1.5.2

server version tradingcalc-mcp

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:15Z	ok_tools	200	241	2024-11-05
2026-08-12T05:34:28Z	ok_tools	200	284	2024-11-05

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.SKalinin909/tradingcalc.svg)](https://robinsaige.com/s/io.github.SKalinin909/tradingcalc)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview