Analytics

l-etf.com

Provides financial market data and analytical tools for leveraged ETF strategies, including SMA signals, calibration, and backtesting.

1 endpoint12 known toolsFirst detected August 5, 2026Last detected August 5, 2026

ENDPOINT 1

https://l-etf.com/mcp

No auth detected

MCP server metadata

Name: l-etf
Version: 1.0.0

Capabilities

tools.listChangedresources.listChangedprompts.listChanged

Known tools 12

list_presets

List the leveraged-ETF presets, risk-off assets, and default SMA settings available to the other l-etf tools.

Inferred read-only

get_market_data

Fetch raw market data over a date range: index total-return prices (`prices`, requires `index`), LETF borrowing rates (`borrowRates`), or CPI inflation (`inflation`).

Inferred read-only

get_sma_signals

Compute the current SMA timing signal (buy/sell/hold) for the S&P 500 and Nasdaq-100 using the given SMA periods and buffers.

Inferred read-only

get_sma_calibration

Return the precomputed best SMA period/buffer per index from the latest offline calibration run.

Inferred read-only

run_backtest

Backtest a simulated leveraged-ETF strategy over a date range and return CAGR, max drawdown, Sharpe, final multiple, trade log, and a 1x benchmark.

Potential side effects

compare_backtests

Backtest several presets over ONE shared date range and compare their metrics.

Inferred read-only

run_rolling_window_analysis

Evaluate one leveraged-ETF strategy across every historical rolling window of `windowLength` years and return the outcome distribution: average/best/worst return, average and worst drawdown, and win rate.

Inferred read-only

run_holding_period_analysis

Show how a strategy's outcome distribution (avg return, win rate, drawdown) changes with the holding period, by running the rolling-window analysis at several window lengths (years).

Inferred read-only

compare_strategies

Rank variants of a leveraged-ETF strategy across historical rolling windows.

Inferred read-only

compare_letfs

Compare simulated leveraged-ETF presets (UPRO, TQQQ, SSO, QLD) across every historical rolling window and return percentile outcome distributions (p10/p50/p90 CAGR and final multiple, win rate vs 1x, median drawdown).

Inferred read-only

get_box_spread_apy

Fetch SPX box-spread implied financing APYs (a low-risk synthetic borrowing rate) live from boxtrades.com.

Inferred read-only

run_futures_backtest

Backtest an SMA timing strategy using index futures (ES/NQ) at a chosen target leverage, with optional leverage cap, quarterly rolls, per-contract fees, and cash-sweep interest.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.l-etf]
url = "https://l-etf.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "l-etf": {
      "type": "http",
      "url": "https://l-etf.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: l-etf
Remote MCP URL: https://l-etf.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "l-etf": {
      "url": "https://l-etf.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "l-etf": {
      "type": "http",
      "url": "https://l-etf.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "l-etf",
  "transport": "streamable-http",
  "url": "https://l-etf.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for l-etf.com was fetched 2026-08-07T11:55:42.600Z and is being refreshed.

Trust status Neutral

l-etf.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.