Should my agent depend on the MCP server io.github.Schoasch/backtesting-arena?

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

Backtesting Arena

io.github.Schoasch/backtesting-arena

Crypto backtesting & Bitcoin cycle analytics. Point-in-time, DSR-corrected, look-ahead-aware.

— the operator's own registry description reported

Publisher io.github.Schoasch · first seen 2026-08-12 · endpoint https://tradingstrategies.work/api/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.387 (moderate). 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

latency229 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools77

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_b862f13694c92b99a9d68581 · 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

arena_cancel_subscription arena_check_subscription_updates arena_compare_strategies arena_dip_decision arena_dip_scenario arena_get_altcoin_season arena_get_altcoin_season_history arena_get_backtest arena_get_backtest_trades arena_get_btc_macro_correlations arena_get_btc_market_structure arena_get_bullmarket_ampel arena_get_cycle arena_get_cycle_history arena_get_drift_log arena_get_edge_reports arena_get_etf_flows arena_get_fear_greed arena_get_filter_insights arena_get_funding_rate arena_get_funding_rate_history arena_get_gem_score arena_get_gem_scores arena_get_gem_validation arena_get_hash_ribbons arena_get_historical_analog arena_get_indicator_snapshot arena_get_iv_snapshot arena_get_job_status arena_get_key_levels arena_get_knowledge arena_get_macro_regime arena_get_max_pain arena_get_max_pain_history arena_get_mayer_multiple arena_get_mayer_multiple_history arena_get_onchain_history arena_get_onchain_latest arena_get_ontology_term arena_get_pulse arena_get_pulse_history arena_get_report_status arena_get_robustness_field arena_get_sentiment arena_get_shared_backtest arena_get_signal_status arena_get_spot_price arena_get_stablecoin_supply arena_get_sth_cost_basis arena_get_strategy_filter_effect arena_get_strategy_insights arena_get_strategy_performance arena_get_strategy_performance_by_regime arena_get_trend_channels arena_get_universe arena_get_volatility_history arena_get_volatility_insights arena_get_volatility_phases arena_get_volatility_recommendations arena_get_winners arena_is_distinguishable arena_list_backtests arena_list_knowledge arena_list_onchain_series arena_list_strategies arena_list_subscriptions arena_list_universes arena_quote_report arena_run_backtest arena_run_grid_backtest arena_run_universe_backtest arena_subscribe_bullmarket_stage arena_subscribe_cycle_changes arena_subscribe_pulse_changes arena_subscribe_signal_alerts get_more_tools validate_strategy

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	77/77	✓
has a description	77/77	✓
description is substantive	77/77	✓
parameters are typed	77/77	✓
parameters are described	77/77	✓

77 of 77 tools graded · 77 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

2025-06-18

protocol version

—

session model

1.5.0

server version backtesting-arena

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	229	2025-06-18
2026-08-12T05:34:28Z	ok_tools	200	201	2025-06-18

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.Schoasch/backtesting-arena.svg)](https://robinsaige.com/s/io.github.Schoasch/backtesting-arena)

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