marketheist

endpoint

https://marketheist.io/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is marketheist live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is marketheist free to use?

Yes — the hub reached it with no key and no payment.

What tools does marketheist have?

10 tools: fund_history, portfolio_returns, portfolio_risk, compare_portfolios, list_portfolios, run_backtest, list_indicators, analyze_portfolio, ….

Is marketheist safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• find_guides open 1h ago

  Search MarketHeist's 90 published research pages and get the page's own verdict and numbers, with its URL to cite: 18 strategy guides (60/40, All Weather, Golden Butterfly, DCA vs lump sum, ...), 26 fund-history pages (how far back an ETF can be tested), 18 trend-filter pages (what a 10-month trend filter did to each portfolio), 16 risk breakdowns (share of risk vs share of money) and 12 rule-robustness pages (does the 200-day average or the golden cross survive other settings, costs and held-out years). Each result returns the title, current verdict, 3-7 headline numbers with the data month, and the last change-log entries. Use it to give a sourced, dated answer to 'does the 200-day average work on SPY', 'would a trend filter have helped All Weather in 2022', 'how far back does VXUS go'. `query` is free words, a ticker or a portfolio name; `slug` returns one page in full (e.g. 'risk/classic-60-40', 'robustness/sma-200-spy'). Read-only and precomputed from the monthly refresh. For live numbers on your own allocation use analyze_portfolio or run_backtest.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233

  {
    "type": "object",
    "properties": {
      "set": {
        "enum": [
          "any",
          "strategies",
          "history",
          "trend",
          "risk",
          "robustness"
        ],
        "type": "string",
        "default": "any",
        "description": "Restrict to one page set: strategies, history, trend, risk or robustness. Default any."
      },
      "slug": {
        "type": "string",
        "description": "Exact page as '<set>/<id>', e.g. 'risk/classic-60-40' or 'robustness/sma-200-spy'. Returns that page in full (every number, labels, change log); `query` is ignored."
      },
      "limit": {
        "type": "integer",
        "default": 5,
        "maximum": 10,
        "minimum": 1,
        "description": "Maximum results for a search (1-10). Default 5."
      },
      "query": {
        "type": "string",
        "description": "Words, a ticker or a portfolio name, e.g. '200-day SPY', 'all weather trend', 'VXUS', 'golden cross'."
      }
    }
  }

  arguments 33 lines copy
• fund_history unknown never probed

  Tell how far back a fund can be tested on MarketHeist once its history is extended with older substitute funds: the proxy chain (e.g. VXUS <- VGTSX), the extended start month, the ETF's own first month and, for the 26 funds with a history page, how closely each stand-in tracked the ETF while both existed (grade close / approximate / stand-in, worst tracking error), the extended-history vs ETF-only CAGR and how many S&P 500 declines the extension adds. Use it for 'can I backtest VXUS to 2000', 'how reliable is the pre-2011 data for BND', before quoting any long-run number for a fund. One `ticker` per call (e.g. VXUS, VTI, TLT, GLD). Read-only and static: no market-data fetch. A ticker with no proxy chain starts at its own inception. For returns of the fund use portfolio_returns; for the rules behind a portfolio's start date use analyze_portfolio.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "ticker"
    ],
    "properties": {
      "ticker": {
        "type": "string",
        "description": "Fund or ETF ticker, e.g. VXUS, VTI, BND, TLT, GLD, DBMF. Case-insensitive; one ticker per call."
      }
    }
  }

  arguments 12 lines copy
• portfolio_returns unknown never probed

  Look up how a portfolio, strategy or fund actually returned: seasonality by calendar month (average return, share of positive months, number of years and a t-statistic so a thin 'September effect' is not presented as a law), calendar-year returns with partial years labelled (optionally next to the S&P 500), trailing 1/3/5/10/20/30-year returns, and the best and worst year and month. Use it for 'is September bad for 60/40', 'what did All Weather return in 2022', 'how has SPY done over 10 years', 'what did my own portfolio return each year'. Pass exactly one of `template` (e.g. all-weather, classic-60-40), `strategy` (e.g. dual-momentum-gem), `ticker` (any Yahoo ticker) or `assets` (your own allocation, including nested portfolios, rotations and strategies as holdings via `sleeve`, with optional `rebalance` and `overlay`); list_portfolios shows every valid id. Built-in ids and the funds with a history page are precomputed from the monthly refresh (instant); other tickers and `assets` are computed live from market data (proxy-extended monthly total returns). Read-only; every answer says which month the data runs through. For risk and drawdowns use portfolio_risk; to compare portfolios use compare_portfolios.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104

  {
    "type": "object",
    "properties": {
      "label": {
        "type": "string",
        "description": "Optional display name for a custom `assets` portfolio. Default \"Custom portfolio\"."
      },
      "years": {
        "type": "integer",
        "maximum": 60,
        "minimum": 1,
        "description": "Limit the calendar-year table to the most recent N years (e.g. 10). Default: all years."
      },
      "assets": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "weight"
          ],
          "properties": {
            "sleeve": {
              "type": "object",
              "description": "Advanced: a strategy node instead of a plain ticker — the app's SleeveRef, resolved server-side. Supported: a rotation/selection (`{source:'selection', config:{universe:[{ticker}], signal:{kind:'indicator', indicatorId, params} | {kind:'trailing-return', lookbackMonths, skipMonths (>= 1; the ranking for a month only sees data through the previous month-end)}, topK, weighting, rebalance}, label}`), a strategy-over-node (`{source:'strategy-over', child:{ticker}, config:<BacktestConfig>, label}`), a saved strategy preset (`{source:'backtest-live', ticker, frequency, config, presetId, label}`), a curated public-library strategy (`{source:'backtest-public', strategyId, label}`), a published backtest share (`{source:'backtest-share', shareId, label}`), a gallery template (`{source:'portfolio-public', templateId, label}`), or a nested portfolio (`{source:'portfolio-mine', portfolioId, config, label}`). Strategies with a config get a node-level overfit check (a share carries only its frozen curve, so no overfit).",
              "additionalProperties": true
            },
            "ticker": {
              "type": "string",
              "description": "Yahoo Finance ticker, e.g. VTI, BND, GLD. Omit when `sleeve` is given."
            },
            "weight": {
              "type": "number",
              "description": "Target weight in percent."
            }
          }
        },
        "description": "Your own allocation instead of an id, computed live (monthly composition, proxy-extended). Same format as analyze_portfolio: plain tickers and nested portfolios, rotations or strategies via `sleeve`. Weights in percent, summing to ~100."
      },
      "ticker": {
        "type": "string",
        "description": "A Yahoo Finance ticker, e.g. SPY, VTI, TLT, AAPL. Funds held by the built-in portfolios or with a history page are precomputed; any other ticker is computed live (proxy-extended where a proxy chain exists)."
      },
      "overlay": {
        "type": "object",
        "required": [
          "kind",
          "months"
        ],
        "properties": {
          "kind": {
            "enum": [
              "trend-filter"
            ],
            "type": "string"
          },
          "months": {
            "type": "number",
            "description": "Moving-average window in months (≥ 2, e.g. 10)."
          }
        },
        "description": "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 (a 10-month filter ≈ the classic 200-day one)."
      },
      "sections": {
        "type": "array",
        "items": {
          "enum": [
            "seasonality",
            "calendar_years",
            "trailing"
          ],
          "type": "string"
        },
        "description": "Which tables to return: seasonality, calendar_years, trailing. Default: all three."
      },
      "strategy": {
        "type": "string",
        "description": "Canonical rule-based strategy id, e.g. 'dual-momentum-gem' or 'faber-trend-timing'. list_portfolios shows all 7."
      },
      "template": {
        "type": "string",
        "description": "Built-in model portfolio id, e.g. 'all-weather' or 'classic-60-40'. list_portfolios shows all 19."
      },
      "benchmark": {
        "enum": [
          "none",
          "sp500"
        ],
        "type": "string",
        "default": "sp500",
        "description": "'sp500' adds S&P 500 (SPY, proxy-extended) columns over the same months and the difference. Default sp500."
      },
      "rebalance": {
        "enum": [
          "none",
          "monthly",
          "quarterly",
          "yearly"
        ],
        "type": "string",
        "default": "yearly",
        "description": "Rebalancing cadence for custom portfolios (templates use their own)."
      }
    }
  }

  arguments 104 lines copy
• portfolio_risk unknown never probed

  Answer both 'how bad did it get' and 'is it really diversified' for a built-in model portfolio, a canonical strategy or your own portfolio. Drawdowns: the deepest peak-to-trough episodes with months to trough and recovery, Ulcer index, longest time underwater, monthly VaR/CVaR 95, worst month and year, and returns in 2008, 2020 and 2022. Diversification: each holding's share of the risk next to its share of the money (60/40 is about 60% of the money and 93% of the risk), the number of independent bets over the full window, the last 10 years and the 36 months to Feb 2009 and Dec 2022, co-movement groups, near-duplicate pairs and the equal-risk weights. Correlations: the holdings' correlation matrix. Pass exactly one of `template` (e.g. classic-60-40, all-weather), `strategy` (e.g. faber-trend-timing) or `assets` (your own allocation, including nested portfolios, rotations and strategies as holdings via `sleeve`, with optional `rebalance` and `overlay`); list_portfolios shows valid ids. `sections` limits the output. Ids are precomputed from the monthly refresh (instant); `assets` are computed live, with independent bets over the full window (and the last 10 years for plain tickers); the 2008 and 2022 windows are computed for built-in portfolios only. Read-only. For headline CAGR/Sharpe use analyze_portfolio; for calendar returns use portfolio_returns.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192

  {
    "type": "object",
    "properties": {
      "label": {
        "type": "string",
        "description": "Optional display name for a custom `assets` portfolio. Default \"Custom portfolio\"."
      },
      "assets": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "weight"
          ],
          "properties": {
            "sleeve": {
              "type": "object",
              "description": "Advanced: a strategy node instead of a plain ticker — the app's SleeveRef, resolved server-side. Supported: a rotation/selection (`{source:'selection', config:{universe:[{ticker}], signal:{kind:'indicator', indicatorId, params} | {kind:'trailing-return', lookbackMonths, skipMonths (>= 1; the ranking for a month only sees data through the previous month-end)}, topK, weighting, rebalance}, label}`), a strategy-over-node (`{source:'strategy-over', child:{ticker}, config:<BacktestConfig>, label}`), a saved strategy preset (`{source:'backtest-live', ticker, frequency, config, presetId, label}`), a curated public-library strategy (`{source:'backtest-public', strategyId, label}`), a published backtest share (`{source:'backtest-share', shareId, label}`), a gallery template (`{source:'portfolio-public', templateId, label}`), or a nested portfolio (`{source:'portfolio-mine', portfolioId, config, label}`). Strategies with a config get a node-level overfit check (a share carries only its frozen curve, so no overfit).",
              "additionalProperties": true
            },
            "ticker": {
              "type": "string",
              "description": "Yahoo Finance ticker, e.g. VTI, BND, GLD. Omit when `sleeve` is given."
            },
            "weight": {
              "type": "number",
              "description": "Target weight in percent."
            }
          }
        },
        "description": "Your own allocation instead of an id, computed live (drawdowns, risk share, bets and correlations of your own mix). Same format as analyze_portfolio: plain tickers and nested portfolios, rotations or strategies via `sleeve`. Weights in percent, summing to ~100."
      },
      "overlay": {
        "type": "object",
        "required": [
          "kind",
          "months"
        ],
        "properties": {
          "kind": {
            "enum": [
              "trend-filter"
            ],
            "type": "string"
          },
          "months": {
            "type": "number",
            "description": "Moving-average window in months (≥ 2, e.g. 10)."
          }
        },
        "description": "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 (a 10-month filter ≈ the classic 200-day one)."
      },
      "episodes": {
        "type": "integer",
        "default": 5,
        "maximum": 8,
        "minimum": 1,
        "description": "How many of the deepest drawdown episodes to list (1-8). Default 5."
      },
      "sections": {
        "type": "array",
        "items": {
          "enum": [
            "drawdowns",
            "diversification",
            "correlations"
          ],
          "type": "string"
        },
        "description": "Which parts to return: drawdowns, diversification, correlations. Default: all three."
      },
      "strategy": {
        "type": "string",
        "description": "Canonical rule-based strategy id, e.g. 'faber-trend-timing'. A strategy is one rule-based line, so its diversification section is reported as not applicable."
      },
      "template": {
        "type": "string",
        "description": "Built-in model portfolio id, e.g. 'classic-60-40', 'all-weather', 'golden-butterfly'. list_portfolios shows all 19."
      },
      "rebalance": {
        "enum": [
          "none",
          "monthly",
          "quarterly",
          "yearly"
        ],
        "type": "string",
        "default": "yearly",
        "description": "Rebalancing cadence for custom portfolios (templates use their own)."
      }
    }
  }

  arguments 92 lines copy
• compare_portfolios unknown never probed

  Compare 2 to 4 portfolios (built-in model portfolios, canonical strategies or your own allocations) side by side over their COMMON window, which is the only fair comparison: two pages' headline numbers usually cover different periods (a portfolio holding gold starts in 2004, the Ivy portfolio in 1996). Returns CAGR, volatility, max drawdown, Sharpe, Sortino, Ulcer index, best/worst year and longest time underwater on the aligned months, each portfolio's own full-window figures (labelled with their start), the pairwise correlation of their monthly returns and a calendar-year table. Use it for 'All Weather vs Golden Butterfly vs 60/40', 'which of these held up better', 'my portfolio vs 60/40'. Each item in `portfolios` has exactly one of `template` or `strategy` (ids from list_portfolios) or `assets` (your own allocation, including nested portfolios, rotations and strategies as holdings, with optional `rebalance` and `overlay`), plus an optional `label`. Ids are precomputed from the monthly refresh; `assets` entries are computed live (at most 2 custom entries and 24 distinct tickers per call). Read-only. For one portfolio's detail use analyze_portfolio, portfolio_returns or portfolio_risk.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394

  {
    "type": "object",
    "required": [
      "portfolios"
    ],
    "properties": {
      "years": {
        "type": "integer",
        "default": 10,
        "maximum": 30,
        "minimum": 0,
        "description": "Calendar-year rows to include (most recent N years of the common window; 0 = none). Default 10."
      },
      "portfolios": {
        "type": "array",
        "items": {
          "type": "object",
          "properties": {
            "label": {
              "type": "string",
              "description": "Optional display name for this column."
            },
            "assets": {
              "type": "array",
              "items": {
                "type": "object",
                "required": [
                  "weight"
                ],
                "properties": {
                  "sleeve": {
                    "type": "object",
                    "description": "Advanced: a strategy node instead of a plain ticker — the app's SleeveRef, resolved server-side. Supported: a rotation/selection (`{source:'selection', config:{universe:[{ticker}], signal:{kind:'indicator', indicatorId, params} | {kind:'trailing-return', lookbackMonths, skipMonths (>= 1; the ranking for a month only sees data through the previous month-end)}, topK, weighting, rebalance}, label}`), a strategy-over-node (`{source:'strategy-over', child:{ticker}, config:<BacktestConfig>, label}`), a saved strategy preset (`{source:'backtest-live', ticker, frequency, config, presetId, label}`), a curated public-library strategy (`{source:'backtest-public', strategyId, label}`), a published backtest share (`{source:'backtest-share', shareId, label}`), a gallery template (`{source:'portfolio-public', templateId, label}`), or a nested portfolio (`{source:'portfolio-mine', portfolioId, config, label}`). Strategies with a config get a node-level overfit check (a share carries only its frozen curve, so no overfit).",
                    "additionalProperties": true
                  },
                  "ticker": {
                    "type": "string",
                    "description": "Yahoo Finance ticker, e.g. VTI, BND, GLD. Omit when `sleeve` is given."
                  },
                  "weight": {
                    "type": "number",
                    "description": "Target weight in percent."
                  }
                }
              },
              "description": "Your own allocation instead of an id, computed live. Same format as analyze_portfolio's `assets` (plain tickers, or nested portfolios, rotations and strategies via `sleeve`)."
            },
            "overlay": {
              "type": "object",
              "required": [
                "kind",
                "months"
              ],
              "properties": {
                "kind": {
                  "enum": [
                    "trend-filter"
                  ],
                  "type": "string"
                },
                "months": {
                  "type": "number",
                  "description": "Moving-average window in months (≥ 2, e.g. 10)."
                }
              },
              "description": "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 (a 10-month filter ≈ the classic 200-day one)."
            },
            "strategy": {
              "type": "string",
              "description": "Canonical strategy id (list_portfolios shows all 7)."
            },
            "template": {
              "type": "string",
              "description": "Built-in model portfolio id (list_portfolios shows all 19)."
            },
            "rebalance": {
              "enum": [
                "none",
                "monthly",
                "quarterly",
                "yearly"
              ],
              "type": "string",
              "default": "yearly",
              "description": "Rebalancing cadence for custom portfolios (templates use their own)."
            }
          }
        },
        "maxItems": 4,
        "minItems": 2,
        "description": "2 to 4 portfolios to compare, e.g. [{\"template\":\"all-weather\"},{\"template\":\"golden-butterfly\"},{\"template\":\"classic-60-40\",\"label\":\"60/40\"}]."
      }
    }
  }

  arguments 94 lines copy
• list_portfolios unknown never probed

  List every portfolio and strategy the other tools accept by id, with a one-line description, holdings, headline CAGR / max drawdown / Sharpe with the start month and the data month, and the marketheist.io page and guide URLs. Three kinds: `template` (19 buy-and-hold model portfolios such as classic-60-40, all-weather, golden-butterfly, permanent; used as `template` in analyze_portfolio, portfolio_returns, portfolio_risk, compare_portfolios, decompose_factors), `strategy` (7 rule-based canonical strategies such as dual-momentum-gem and faber-trend-timing; used as `strategy`), and `library_strategy` (19 curated single-asset backtest strategies, usable as holdings via {source:'backtest-public', strategyId} in analyze_portfolio). Call this first when you do not know an id, to avoid guessing. `query` filters by name, id or a holding ticker (e.g. 'gold', 'TLT'). Read-only and precomputed (data through the stated month); the numbers are full-window headline figures over each entry's own start, so use compare_portfolios for a like-for-like comparison.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "properties": {
      "kind": {
        "enum": [
          "all",
          "template",
          "strategy",
          "library_strategy"
        ],
        "type": "string",
        "default": "all",
        "description": "Which list: template (model portfolios), strategy (canonical rule-based strategies), library_strategy (curated backtest strategies) or all. Default all."
      },
      "query": {
        "type": "string",
        "description": "Optional filter on name, id, description or a holding ticker, e.g. 'gold', 'momentum', 'TLT'."
      }
    }
  }

  arguments 20 lines copy
• run_backtest unknown never probed

  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, and a `cite` block that links the robustness page when the config is a famous setting (200-day average, golden cross, MACD, RSI 30/70 on SPY, QQQ, TLT, GLD or EFA). 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. Single asset only: for allocations use analyze_portfolio. Read-only; live market data, so heavy callers can hit the daily live-data limit.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125

  {
    "type": "object",
    "required": [
      "ticker",
      "indicator_id"
    ],
    "properties": {
      "ticker": {
        "type": "string",
        "description": "Yahoo Finance ticker symbol (e.g. AAPL, ^NDX, BTC-USD, SPY)."
      },
      "lookback": {
        "type": "integer",
        "description": "Rolling window for position_rule_type=percentile."
      },
      "direction": {
        "enum": [
          "above",
          "below"
        ],
        "type": "string",
        "default": "above",
        "description": "Long when indicator is above (or below) threshold/MA/percentile."
      },
      "frequency": {
        "enum": [
          "1d",
          "1wk",
          "1mo"
        ],
        "type": "string",
        "default": "1wk",
        "description": "Bar frequency. Default: 1wk."
      },
      "ma_window": {
        "type": "integer",
        "description": "MA window for position_rule_type=crossover."
      },
      "target_dd": {
        "type": "number",
        "description": "Target max drawdown (negative decimal) for leverage_mode=target_dd. E.g. -0.40."
      },
      "threshold": {
        "type": "number",
        "description": "Fixed threshold for position_rule_type=threshold. E.g. 50 for RSI, 1.0 for MA Crossover. Omit to use the indicator's default rule (the 'Default rule' list_indicators shows; e.g. RSI: above 50)."
      },
      "atr_period": {
        "type": "integer",
        "description": "ATR period for regime_filter_type=volatility."
      },
      "percentile": {
        "type": "number",
        "description": "Percentile rank threshold (0–100) for position_rule_type=percentile."
      },
      "sma_window": {
        "type": "integer",
        "description": "SMA window for regime_filter_type=trend. Classic: 200."
      },
      "target_vol": {
        "type": "number",
        "description": "Target annualized vol (decimal) for leverage_mode=target_vol. E.g. 0.15 = 15%."
      },
      "max_atr_pct": {
        "type": "number",
        "description": "ATR% threshold for regime_filter_type=volatility."
      },
      "indicator_id": {
        "type": "string",
        "description": "Built-in indicator id. Call list_indicators to see all options. Common: rsi, bollinger, ma_crossover, ema_crossover, adx, cci, stochastic."
      },
      "leverage_mode": {
        "enum": [
          "none",
          "fixed",
          "target_vol",
          "target_dd"
        ],
        "type": "string",
        "default": "none",
        "description": "none=1×. fixed=constant multiplier. target_vol=scale to vol target. target_dd=scale to drawdown target."
      },
      "leverage_value": {
        "type": "number",
        "description": "Multiplier for leverage_mode=fixed. E.g. 2.0 = 2×."
      },
      "execution_delay": {
        "type": "integer",
        "default": 1,
        "maximum": 5,
        "minimum": 0,
        "description": "Bars of delay between signal and execution. Use 1 to avoid lookahead bias."
      },
      "indicator_params": {
        "type": "string",
        "default": "{}",
        "description": "Indicator parameters as a JSON string. E.g. '{\"period\":14}' for RSI. Omit to use defaults."
      },
      "position_rule_type": {
        "enum": [
          "threshold",
          "crossover",
          "percentile"
        ],
        "type": "string",
        "default": "threshold",
        "description": "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": {
        "enum": [
          "none",
          "trend",
          "volatility"
        ],
        "type": "string",
        "default": "none",
        "description": "trend: only hold when close > SMA(sma_window). volatility: only hold when ATR% < max_atr_pct."
      },
      "transaction_costs_bps": {
        "type": "number",
        "default": 0,
        "minimum": 0,
        "description": "One-way transaction cost in basis points (1 bps = 0.01%)."
      }
    }
  }

  arguments 125 lines copy
• list_indicators unknown never probed

  List the built-in technical indicators available for backtesting (RSI, moving-average crossovers, ADX, Bollinger, CCI, Stochastic, and more) with their IDs, parameters with defaults, and each indicator's default long rule. Call this to answer what strategies or indicators can be tested, or before run_backtest when unsure which indicator_id or parameters to use. Takes no arguments. Read-only and static (no market data is fetched, never rate-limited by the live budget). To find portfolios and strategies instead, use list_portfolios.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• analyze_portfolio unknown 1h ago

  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: CAGR, max drawdown, volatility, Sharpe, Sortino, Ulcer index, $10,000 growth, the number of independent bets (holdings whose returns average a correlation of 0.5 or more count as one group, then the effective count of groups by risk share), the top risk driver, trailing Sharpe, and a `validity` block (provenance, caveats, a reproduce-me hash) plus a `cite` block with the marketheist.io pages that show the same numbers. Use it for 'how did 60/40 / All Weather / Golden Butterfly perform' or for a custom mix. Provide exactly one of: a `template` id (19 model portfolios, listed in list_portfolios), a `strategy` id (7 rule-based canonical strategies, e.g. dual-momentum-gem) or a custom `assets` allocation (plain tickers and nested portfolios, rotations, strategies as holdings via `sleeve`). Template and strategy ids are answered from precomputed data through the stated month (instant, not rate-limited); custom assets and an `overlay` are computed live from market data. For seasonality and calendar years use portfolio_returns; for drawdown episodes and diversification use portfolio_risk; to compare portfolios use compare_portfolios. Read-only; surface the caveats when reporting.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103

  {
    "type": "object",
    "properties": {
      "label": {
        "type": "string",
        "description": "Optional display name for a custom `assets` portfolio. Default \"Custom portfolio\"."
      },
      "assets": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "weight"
          ],
          "properties": {
            "sleeve": {
              "type": "object",
              "description": "Advanced: a strategy node instead of a plain ticker — the app's SleeveRef, resolved server-side. Supported: a rotation/selection (`{source:'selection', config:{universe:[{ticker}], signal:{kind:'indicator', indicatorId, params} | {kind:'trailing-return', lookbackMonths, skipMonths (>= 1; the ranking for a month only sees data through the previous month-end)}, topK, weighting, rebalance}, label}`), a strategy-over-node (`{source:'strategy-over', child:{ticker}, config:<BacktestConfig>, label}`), a saved strategy preset (`{source:'backtest-live', ticker, frequency, config, presetId, label}`), a curated public-library strategy (`{source:'backtest-public', strategyId, label}`), a published backtest share (`{source:'backtest-share', shareId, label}`), a gallery template (`{source:'portfolio-public', templateId, label}`), or a nested portfolio (`{source:'portfolio-mine', portfolioId, config, label}`). Strategies with a config get a node-level overfit check (a share carries only its frozen curve, so no overfit).",
              "additionalProperties": true
            },
            "ticker": {
              "type": "string",
              "description": "Yahoo Finance ticker, e.g. VTI, BND, GLD. Omit when `sleeve` is given."
            },
            "weight": {
              "type": "number",
              "description": "Target weight in percent."
            }
          }
        },
        "description": "Custom allocation (omit if using `template` or `strategy`). Weights are percentages summing to ~100. A holding is a plain ticker OR a strategy node via `sleeve`."
      },
      "overlay": {
        "type": "object",
        "required": [
          "kind",
          "months"
        ],
        "properties": {
          "kind": {
            "enum": [
              "trend-filter"
            ],
            "type": "string"
          },
          "months": {
            "type": "number",
            "description": "Moving-average window in months (≥ 2, e.g. 10)."
          }
        },
        "description": "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 (a 10-month filter ≈ the classic 200-day one)."
      },
      "strategy": {
        "enum": [
          "dual-momentum-gem",
          "tsmom-sp500",
          "faber-trend-timing",
          "sector-momentum-rotation",
          "risk-parity-inverse-vol",
          "gtaa-aggressive",
          "adaptive-asset-allocation"
        ],
        "type": "string",
        "description": "Canonical rule-based strategy to analyze. One of: dual-momentum-gem, tsmom-sp500, faber-trend-timing, sector-momentum-rotation, risk-parity-inverse-vol, gtaa-aggressive, adaptive-asset-allocation. Answered from precomputed data. Omit when using `template` or `assets`."
      },
      "template": {
        "enum": [
          "golden-butterfly",
          "all-weather",
          "permanent",
          "dragon",
          "faber-ivy",
          "faber-gaa",
          "bogleheads-3fund",
          "wealthfront-classic",
          "betterment-core",
          "classic-60-40",
          "classic-40-60",
          "swensen",
          "ferri-core-four",
          "couch-potato",
          "coffeehouse",
          "no-brainer",
          "larry",
          "buffett-90-10",
          "total-sp500"
        ],
        "type": "string",
        "description": "Built-in model portfolio to analyze. One of: golden-butterfly, all-weather, permanent, dragon, faber-ivy, faber-gaa, bogleheads-3fund, wealthfront-classic, betterment-core, classic-60-40, classic-40-60, swensen, ferri-core-four, couch-potato, coffeehouse, no-brainer, larry, buffett-90-10, total-sp500. Omit to analyze a custom `assets` allocation instead."
      },
      "rebalance": {
        "enum": [
          "none",
          "monthly",
          "quarterly",
          "yearly"
        ],
        "type": "string",
        "default": "yearly",
        "description": "Rebalancing cadence for custom portfolios (templates use their own)."
      }
    }
  }

  arguments 103 lines copy
• decompose_factors unknown 1h ago

  Explain WHAT DRIVES the returns of a ticker, ETF or built-in portfolio 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 a return is just market beta, whether it has real alpha, or what is driving a portfolio's returns. Returns betas (loadings), t-stats, an additive variance decomposition (shares sum to R²), annualized alpha, idiosyncratic vs total volatility, and for a portfolio the holdings that drive each factor. Computed by OLS regression on real price history via tradeable ETF proxies (long-short factor spreads): measured exposure, not a forecast. Provide exactly one of `target` (a ticker, computed live), `template` (a built-in model portfolio), `strategy` (a canonical strategy) or `assets` (your own allocation, including nested portfolios, rotations and strategies as holdings, computed live); portfolio ids are answered from precomputed monthly data through the stated month. Portfolios (ids and `assets`) use the five default factors (market, size, value, duration, credit), are monthly and ignore `frequency` and `factors`. For performance numbers use analyze_portfolio. Read-only.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124

  {
    "type": "object",
    "properties": {
      "label": {
        "type": "string",
        "description": "Optional display name for a custom `assets` portfolio. Default \"Custom portfolio\"."
      },
      "assets": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "weight"
          ],
          "properties": {
            "sleeve": {
              "type": "object",
              "description": "Advanced: a strategy node instead of a plain ticker — the app's SleeveRef, resolved server-side. Supported: a rotation/selection (`{source:'selection', config:{universe:[{ticker}], signal:{kind:'indicator', indicatorId, params} | {kind:'trailing-return', lookbackMonths, skipMonths (>= 1; the ranking for a month only sees data through the previous month-end)}, topK, weighting, rebalance}, label}`), a strategy-over-node (`{source:'strategy-over', child:{ticker}, config:<BacktestConfig>, label}`), a saved strategy preset (`{source:'backtest-live', ticker, frequency, config, presetId, label}`), a curated public-library strategy (`{source:'backtest-public', strategyId, label}`), a published backtest share (`{source:'backtest-share', shareId, label}`), a gallery template (`{source:'portfolio-public', templateId, label}`), or a nested portfolio (`{source:'portfolio-mine', portfolioId, config, label}`). Strategies with a config get a node-level overfit check (a share carries only its frozen curve, so no overfit).",
              "additionalProperties": true
            },
            "ticker": {
              "type": "string",
              "description": "Yahoo Finance ticker, e.g. VTI, BND, GLD. Omit when `sleeve` is given."
            },
            "weight": {
              "type": "number",
              "description": "Target weight in percent."
            }
          }
        },
        "description": "Your own allocation instead of an id, computed live (monthly, default factors; the answer also lists the holdings behind each factor). Same format as analyze_portfolio: plain tickers and nested portfolios, rotations or strategies via `sleeve`. Weights in percent, summing to ~100."
      },
      "target": {
        "type": "string",
        "description": "Yahoo Finance ticker to decompose, e.g. AAPL, QQQ, TLT, ARKK. Omit when using `template` or `strategy`."
      },
      "factors": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "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 history from ~2011-2013, which shortens the analyzable window — factors without enough overlap are dropped and reported."
      },
      "overlay": {
        "type": "object",
        "required": [
          "kind",
          "months"
        ],
        "properties": {
          "kind": {
            "enum": [
              "trend-filter"
            ],
            "type": "string"
          },
          "months": {
            "type": "number",
            "description": "Moving-average window in months (≥ 2, e.g. 10)."
          }
        },
        "description": "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 (a 10-month filter ≈ the classic 200-day one)."
      },
      "strategy": {
        "enum": [
          "dual-momentum-gem",
          "tsmom-sp500",
          "faber-trend-timing",
          "sector-momentum-rotation",
          "risk-parity-inverse-vol",
          "gtaa-aggressive",
          "adaptive-asset-allocation"
        ],
        "type": "string",
        "description": "Canonical rule-based strategy whose returns to decompose, e.g. dual-momentum-gem. One of: dual-momentum-gem, tsmom-sp500, faber-trend-timing, sector-momentum-rotation, risk-parity-inverse-vol, gtaa-aggressive, adaptive-asset-allocation. Precomputed; default factors."
      },
      "template": {
        "enum": [
          "golden-butterfly",
          "all-weather",
          "permanent",
          "dragon",
          "faber-ivy",
          "faber-gaa",
          "bogleheads-3fund",
          "wealthfront-classic",
          "betterment-core",
          "classic-60-40",
          "classic-40-60",
          "swensen",
          "ferri-core-four",
          "couch-potato",
          "coffeehouse",
          "no-brainer",
          "larry",
          "buffett-90-10",
          "total-sp500"
        ],
        "type": "string",
        "description": "Built-in model portfolio whose returns to decompose, e.g. all-weather. One of: golden-butterfly, all-weather, permanent, dragon, faber-ivy, faber-gaa, bogleheads-3fund, wealthfront-classic, betterment-core, classic-60-40, classic-40-60, swensen, ferri-core-four, couch-potato, coffeehouse, no-brainer, larry, buffett-90-10, total-sp500. Precomputed; default factors."
      },
      "frequency": {
        "enum": [
          "1d",
          "1wk",
          "1mo"
        ],
        "type": "string",
        "default": "1mo",
        "description": "Return frequency for the regression of a `target` ticker. Monthly (default) is standard for factor analysis. Ignored for `template` / `strategy` (always monthly)."
      },
      "rebalance": {
        "enum": [
          "none",
          "monthly",
          "quarterly",
          "yearly"
        ],
        "type": "string",
        "default": "yearly",
        "description": "Rebalancing cadence for custom portfolios (templates use their own)."
      }
    }
  }

  arguments 124 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

• api.marketheist.io mcp · 5 tools