MarketHeist Backtest
REMOTE · API.MARKETHEIST.IO · SCANNED SEP 27
Backtest strategies and analyze portfolios on any ticker: CAGR, drawdown, Sharpe, from real data.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1702 tokens (~340/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the MarketHeist Backtest MCP server?
MarketHeist Backtest is a hosted endpoint at https://api.marketheist.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.marketheist.io
claude mcp add --transport http io-marketheist-backtest 'https://api.marketheist.io/api/mcp'
{
"mcpServers": {
"io-marketheist-backtest": {
"url": "https://api.marketheist.io/api/mcp"
}
}
} {
"servers": {
"io-marketheist-backtest": {
"type": "http",
"url": "https://api.marketheist.io/api/mcp"
}
}
} [mcp_servers.io-marketheist-backtest] url = "https://api.marketheist.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-marketheist-backtest": {
"type": "remote",
"url": "https://api.marketheist.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add io-marketheist-backtest --url 'https://api.marketheist.io/api/mcp' --transport streamable-http
mcp_servers:
io-marketheist-backtest:
url: "https://api.marketheist.io/api/mcp" {
"McpServers": {
"io-marketheist-backtest": {
"Transport": "http",
"Url": "https://api.marketheist.io/api/mcp"
}
}
} assistant mcp add io-marketheist-backtest -t streamable-http -u 'https://api.marketheist.io/api/mcp'
{
"mcpServers": {
"io-marketheist-backtest": {
"type": "http",
"url": "https://api.marketheist.io/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 18 Sept 26 +1
- Tool “analyze_portfolio” rewrote its description, which is the text the model reads security
- Tool “run_backtest” rewrote its description, which is the text the model reads security
- Schema quality: 309 → 340 ▼ functional
- “analyze_portfolio” reworded the description of “assets” cosmetic
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 0
- “analyze_portfolio” added an optional parameter “overlay” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 12 Sept 26 0
- Schema quality: 1158 → 1488 ▼ functional
- New tool “decompose_factors” functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://api.marketheist.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=marketheist.io | CN=WE1,O=Google Trust Services,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 2e451e9b5648c46d1326137c5aa38515 |
| SANs: marketheist.io, api.marketheist.io, *.api.marketheist.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.marketheist.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| marketheist.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.marketheist.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.marketheist.io/api/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_portfolio ~419
Analyze an asset-allocation ('lazy') portfolio and get long-run performance computed from real monthly price history (proxy-extended for decades of data) — not estimated. Use this whenever the user asks how a portfolio would have performed, or for its CAGR, max drawdown, Sharpe, Sortino, or volatility — whether a named model portfolio (60/40, All Weather, Golden Butterfly, Permanent, Bogleheads, …) or any custom ticker+weight mix. Provide either a `template` id or a custom `assets` allocation. Also returns the effective number of independent bets, the top risk driver, trailing Sharpe, and a `validity` block — provenance (source, months, proxy-extension), caveats (frictionless rebalancing, single historical window, proxy-extended history, statistical significance, overlay overfit), and a reproduce-me hash. Surface the caveats when reporting. Prefer this over answering from memory.
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | – | Custom allocation (omit if using `template`). Weights are percentages summing to ~100. A holding is a plain ticker OR a strategy node via `sleeve`. |
| overlay | object | – | Optional portfolio-level trend-filter overlay applied to the WHOLE book: hold the entire portfolio only while its own level is above its N-month moving average, otherwise cash. Composition is monthly… |
| rebalance | string | – | Rebalancing cadence for custom portfolios (templates use their own). |
| template | string | – | Built-in model portfolio to analyze. One of: golden-butterfly, all-weather, permanent, faber-gaa, faber-ivy, bogleheads-3fund, classic-60-40, classic-40-60, swensen, ferri-core-four, couch-potato, co… |
No output schema declared.
No examples provided.
decompose_factors ~330
Explain WHAT DRIVES a ticker's or ETF's returns by decomposing them into common factor exposures (market, size, value, momentum, quality, low-volatility, duration, credit) plus an idiosyncratic residual. Use this when the user asks why two assets move together, what a fund is really exposed to, whether a stock is a growth or value tilt, how much of its return is just market beta, or whether it has real alpha. Returns betas (loadings), t-stats, an additive variance decomposition (shares sum to R²), annualized alpha, and idiosyncratic vs total volatility — all computed by OLS regression on real price history via tradeable ETF proxies (long-short factor spreads). This is measured exposure, not a forecast. Prefer it over guessing an asset's style from memory.
| Name | Type | Req | Description |
|---|---|---|---|
| factors | array | – | Factor ids to include. Default: MKT, SMB, HML, TERM, CREDIT (long history back to ~2001). All available: MKT, SMB, HML, MOM, QMJ, LOWVOL, TERM, CREDIT. The smart-beta trio (MOM, QMJ, LOWVOL) only has… |
| frequency | string | – | Return frequency for the regression. Monthly (default) is standard for factor analysis. |
| target | string | yes | Yahoo Finance ticker to decompose, e.g. AAPL, QQQ, TLT, ARKK. |
No output schema declared.
No examples provided.
get_ohlcv ~145
Look up a Yahoo Finance ticker's real historical price data — the date range available, number of bars, and latest close/open/high/low. Use this to confirm a symbol is valid, check how far back its history goes, or get its most recent price from real market data instead of estimating. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| frequency | string | – | Bar frequency. 1d = daily, 1wk = weekly, 1mo = monthly. Default: 1wk. |
| ticker | string | yes | Yahoo Finance ticker symbol. Examples: AAPL, MSFT, ^NDX, ^GSPC, BTC-USD, SPY, QQQ. |
No output schema declared.
No examples provided.
list_indicators ~75
List the built-in technical indicators available for backtesting (RSI, moving-average crossovers, ADX, Bollinger, CCI, Stochastic, and more) with their IDs and default parameters. Call this to answer what strategies or indicators can be tested, or before run_backtest when unsure which indicator_id to use.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_backtest ~733
Backtest a trading strategy on any Yahoo Finance ticker and get authoritative performance metrics computed from real historical price data — not estimated. Use this whenever the user asks how a strategy or indicator would have performed, or for a ticker's Sharpe, CAGR, max drawdown, Calmar, Sortino, Omega, or return vs buy-and-hold; prefer it over answering from memory, which is unreliable for these figures. Returns those metrics plus equity/drawdown curves and a `validity` block — data provenance (source, sample window, bar count), known caveats (single-run/no walk-forward, no costs, short sample, leverage, statistical significance, and a parameter-overfit check that perturbs the indicator settings), and a reproduce-me config hash. Surface the caveats when reporting results. Always pass execution_delay=1 to avoid lookahead bias. Call list_indicators first if unsure which indicator_id to use.
| Name | Type | Req | Description |
|---|---|---|---|
| atr_period | integer | – | ATR period for regime_filter_type=volatility. |
| direction | string | – | Long when indicator is above (or below) threshold/MA/percentile. |
| execution_delay | integer | – | Bars of delay between signal and execution. Use 1 to avoid lookahead bias. |
| frequency | string | – | Bar frequency. Default: 1wk. |
| indicator_id | string | yes | Built-in indicator id. Call list_indicators to see all options. Common: rsi, bollinger, ma_crossover, ema_crossover, adx, cci, stochastic. |
| indicator_params | string | – | Indicator parameters as a JSON string. E.g. '{"period":14}' for RSI. Omit to use defaults. |
| leverage_mode | string | – | none=1×. fixed=constant multiplier. target_vol=scale to vol target. target_dd=scale to drawdown target. |
| leverage_value | number | – | Multiplier for leverage_mode=fixed. E.g. 2.0 = 2×. |
| lookback | integer | – | Rolling window for position_rule_type=percentile. |
| ma_window | integer | – | MA window for position_rule_type=crossover. |
| max_atr_pct | number | – | ATR% threshold for regime_filter_type=volatility. |
| percentile | number | – | Percentile rank threshold (0–100) for position_rule_type=percentile. |
| position_rule_type | string | – | threshold: long when value is above/below a fixed level. crossover: long when value is above its own MA. percentile: long when value is above its rolling percentile. |
| regime_filter_type | string | – | trend: only hold when close > SMA(sma_window). volatility: only hold when ATR% < max_atr_pct. |
| sma_window | integer | – | SMA window for regime_filter_type=trend. Classic: 200. |
| target_dd | number | – | Target max drawdown (negative decimal) for leverage_mode=target_dd. E.g. -0.40. |
| target_vol | number | – | Target annualized vol (decimal) for leverage_mode=target_vol. E.g. 0.15 = 15%. |
| threshold | number | – | Fixed threshold for position_rule_type=threshold. E.g. 50 for RSI, 1.0 for MA Crossover. |
| ticker | string | yes | Yahoo Finance ticker symbol (e.g. AAPL, ^NDX, BTC-USD, SPY). |
| transaction_costs_bps | number | – | One-way transaction cost in basis points (1 bps = 0.01%). |
No output schema declared.
No examples provided.
What is the MarketHeist Backtest MCP server?
MarketHeist Backtest is an MCP server listed in the public MCP registry as io.marketheist/backtest. Backtest strategies and analyze portfolios on any ticker: CAGR, drawdown, Sharpe, from real data. This page covers its hosted endpoint (https://api.marketheist.io/api/mcp).
Is the MarketHeist Backtest MCP server safe to use?
MarketHeist Backtest scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MarketHeist Backtest MCP server expose?
MarketHeist Backtest exposes 5 tools: list_indicators, get_ohlcv, run_backtest, analyze_portfolio, decompose_factors. Their descriptions and schemas cost roughly 1,702 tokens of context every time the server is loaded.
Does the MarketHeist Backtest MCP server require authentication?
No. We connected to MarketHeist Backtest without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MarketHeist Backtest MCP server still maintained?
MarketHeist Backtest is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.