F
licenseNot graded
qualityD
maintenancePulls Binance spot candle data, computes technical indicators (RSI, MACD, EMAs), and evaluates user-defined bias and risk rules without needing a TradingView session.
85 npm
-
Backtester
Server Details
Test a plain-words trading rule on historical prices and compare the trades with SPY. Not advice.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
B3.2/5.0
Scored across 9 tools
Disambiguation4/5
Most tools have distinct purposes: build_series and build_signal target different outputs, get_prices and list_data separate price reads from metadata, and list_strategies/save_strategy/share_report form a clear publishing flow. The main overlap is report vs. simulate, since both involve running a backtest-like workflow, though report focuses on results display and simulate on fills/balances.
Naming Consistency4/5
The set is predominantly consistent snake_case with verb_noun names such as build_series, get_prices, list_data, save_strategy, and share_report. The main deviations are report and simulate, which are verb-like names without an explicit noun object.
Tool Count5/5
Nine tools is well-scoped for a backtesting server, covering data discovery, series/signal construction, simulation/reporting, and publishing without obvious padding. Each tool maps to a meaningful step in the workflow.
Completeness4/5
The surface covers the main lifecycle: discover data, build series and signals, run reports, simulate, save, and share strategies. Minor gaps include no explicit delete or update operation for saved strategies beyond replacement via expectedKey, and no direct get_strategy detail tool.
Available Tools
9 toolsbuild_seriesBuild data seriesCRead-onlyInspect
Build named time series from a run form. Needs version, data, and series.
Inputs: run (required).
build_signalBuild trading signalsCRead-onlyInspect
Build named trading signals from a run form. Needs version, data, series, and signals.
Inputs: run (required).
get_pricesGet historical pricesBRead-onlyInspect
Read historical prices for a run form. Needs only version and data.
Inputs: run (required).
list_dataList available dataARead-onlyInspect
List available price data, fields, dates, limits, and whether reports can be retained for publishing.
Inputs: no named parameters.
list_strategiesList saved strategiesARead-onlyInspect
List published website strategies, their URLs, and their current keys. Use a current key as expectedKey only when the user asks to replace that saved strategy.
Inputs: no named parameters.
reportRun a backtest reportARead-onlyInspect
Run a backtest and show its results. Supply strategyExplanation in plain terms for the widget. In your reply, explain the rule, always show Return vs. SPY (summary.returnVsSpyPct in percentage points, or Unavailable), and give one takeaway or limit supported by the report. Choose any additional cards using stats. Use scoreSeries for a separate score panel. Use chartSeries to select named report series and set their legend labels, line or bar types, colors, and line patterns. Keep the interpretation about this historical test. To publish this exact result later, pass its reportId to save_strategy after the user asks to save it to the website.
Inputs: run (required), stats, chartSeries, scoreSeries, +1 more.
save_strategyPublish a report to the public websiteADestructiveIdempotentInspect
PUBLIC: anyone can see the saved page. Publish a completed report to the public website after the user asks to save it. Use the reportId returned by report, a public slug, and client-authored page and presentation choices. Never submit or invent result numbers. Adds it to the strategy directory without rerunning the strategy. Existing slugs require expectedKey to replace a different result. setAsHome changes the home page only when explicitly requested.
Inputs: id (required), page (required), reportId (required), presentation (required), +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Related MCP Connectors
Backtest any trading setup on the S&P 500 vs random days, and see which stocks matched today.
Backtest plain-English trading strategies on real market data: graded results, honesty flags.
Read-only crypto indicators, risk sizing and rule backtests. Not financial advice.
Find the calendar days, weeks and events that beat simply holding a US stock or ETF, year by year.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables point-in-time backtesting on daily bars with declarative strategy specs and deterministic simulated runs, offering two tool surfaces without needing API keys or network access.10MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for natural-language daily stock/ETF strategy backtesting. It provides constrained tools for strategy specification, data validation, queue-based backtests, and verifiable result artifacts.10 PyPI1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceDeterministic market-state engine for trading agents — zero LLM in the signal path. 8 tools: structural market state & phase, action gate (GO/WATCH/HOLD), entry/target/invalidation coordinates, bar-by-bar state timeline, composed view cards, and pre-trade intent validation. Every output traces to a bar-stamped ledger with a public daily self-scoring track record.3MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.