Robin Saige we check the tools AI agents call

Backtest360

com.backtest360/backtest360

MCP server exposing the Backtest360 engine API as tools for AI agents.

— the operator's own registry description reported

Publisher com.backtest360 · first seen 2026-08-12 · endpoint https://mcp.backtest360.com/mcp

allow
verdict
mid-solo
cluster
ok_tools
answers
20
tools served

Dependency rating derived

allow — mid-solo — safe to depend on

Cluster mid-solo · distinctiveness 0.572 (moderate). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Reach — can an agent get to it?
answersalive_tools
latency369 ms
vs populationtypical
protocolcurrent
authopen
Use — can it use it?
tools20
vs populationmid
capabilities4
harnessB
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

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

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. This server's 20 tools, classified, with what checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public10serves public factstruth-checkable against a public source — the V-ladder applies in full
action9changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified1not yet classifiable from its textTier-1 only until its tools describe themselves

Tools last seen

compare_backtests compute_stats engine_info export_backtest get_catalog get_data_range get_latest_signal get_macro_series get_me get_price_history get_quote get_strategy_schema get_ticker_info list_indicators list_macro_series list_templates list_tickers run_backtest search_tickers 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 B — usable, with rough edges.

legibility checktools passingok
name is clear & specific20/20
has a description20/20
description is substantive20/20
parameters are typed20/20
parameters are described3/203/20

20 of 20 tools graded · 20 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
0.2.4
server version backtest360

Capabilities: experimental prompts resources 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)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:57:57Zok_tools2003692025-06-18
2026-08-12T05:33:13Zok_tools2003692025-06-18

Watch or embed this verdict

verdict badge

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/com.backtest360/backtest360.svg)](https://robinsaige.com/s/com.backtest360/backtest360)

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