ETFIQ

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Independent US ETF data and benchmarks for model portfolios, each figure with its source and date.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "ETFIQ": {
      "url": "https://mcp.etfiq.com",
      "transport": "streamable-http"
    }
  }
}

Measured tools (20)

• etf_search read-only

  Find US listed ETFs by ticker, fund name, or a word from the name. Use this FIRST when the user names a fund loosely, then etf_profile with the ticker it returns. Refuses rather than returning a near match: a refusal says why, and for a fund it means ETFIQ does not publish it. A former ticker (SPLG) answers with the fund it trades as now, and a closed fund with its page and the day it closed. Funds filed with the SEC that do not trade (prediction markets, sports teams) come back in filed, with how many are filed and how many trade, never as results.

  Parameters:

  • query (required) — string
  • desk — string
  • limit — integer

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etf_profile read-only

  Everything ETFIQ publishes about one fund: issuer, category, and each figure with its source and as-of date, plus a one sentence verdict on how it did against what its own label promises. benchmark is the fund's own benchmark as its page names it: its name, how it was set, and the fund's return, the benchmark's and the gap for each window (periods is the page's whole window table). A closed fund answers with closed (the day and the page's words); a former ticker answers as the fund it trades as now, and says so. The ETFIQ benchmarks for model portfolios (list_benchmarks) are a different thing.

  Parameters:

  • ticker (required) — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etf_holdings read-only

  What a fund holds, by weight, and how old that is. ALWAYS read lag_days before presenting it: an issuer file read today and a filing from two months ago both come back here and are not the same answer.

  Parameters:

  • ticker (required) — string
  • top_n — integer

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etf_theme read-only

  Every US listed fund in a theme, largest first, with what each charges and how much of it is already in the S&P 500. USE THIS for any "what X ETFs are there" or "top X ETFs" question: it returns the whole published set rather than a sample.

  Parameters:

  • theme (required) — string
  • limit — integer

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etf_themes read-only

  Every theme ETFIQ publishes and how many funds each holds. Call when unsure what a theme is called, then etf_theme.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etfiq_page read-only

  Read ANY published ETFIQ page as text: a theme hub, a ranking, a comparison of two funds, an issuer, a methodology note, a dated study. Takes a path like /themes/cyber or a full etfiq.com URL. This reaches all 40,000 pages, including everything the typed tools above do not cover, and returns the page content rather than its navigation.

  Parameters:

  • path (required) — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etfiq_sections read-only

  What ETFIQ publishes, section by section, with a page count for each, and start_here: the main pages (fund flows, the weekly flows report, ETF model portfolios and benchmarks, the filed prediction-market and sports-team funds, issuers, methodology, rankings, the screener) with what each holds. Start here when the question is not about one fund.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etfiq_list read-only

  The pages inside one section, optionally filtered to those whose address contains a word. Use after etfiq_sections to find a page, then etfiq_page to read it. The count returned is the whole matching set even when the list is capped.

  Parameters:

  • section (required) — string
  • limit — integer
  • contains — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etf_screen read-only

  Every fund matching some filters, each with its net assets and the source and date that figure came from. Filters: desk, issuer, max_fee_pct, min_assets_usd; and, from the ETFIQ screener, tracks (the index the funds track, such as "S&P 500"), min_yield_pct (12-month yield of at least that percent), pays (payout frequency: weekly, monthly, quarterly, semiannual or annual, published for income ETFs) and sort (assets, largest first; fee, lowest first; yield, highest first). count is the WHOLE matching set: when fewer rows come back, truncated and note say so, and the rows must never be presented as the whole set. first names every fund tied at the top of the order. Use for "find me all X" and "cheapest X" questions rather than repeated searches. Fees are percentages, not basis points. Funds with no published figure for a filter are set aside and counted, not treated as failing it.

  Parameters:

  • desk — string
  • pays — string — Payout frequency, published for income ETFs.
  • sort — string — assets: largest first; fee: lowest first; yield: highest first.
  • limit — integer
  • issuer — string
  • tracks — string — The index the funds track, such as S&P 500.
  • max_fee_pct — number
  • min_yield_pct — number — 12-month yield of at least this many percent (10 is 10%).
  • min_assets_usd — number

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etf_overlap read-only

  How much of their weight two funds hold in common, as ETFIQ published it on the comparison page for that pair. Use when asked whether two ETFs are the same thing, or whether owning both adds anything. Refuses rather than estimating when the pair is not compared or either holdings book is incomplete.

  Parameters:

  • a (required) — string
  • b (required) — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etfiq_as_of read-only

  What ETFIQ published on a given date, from its frozen dated archive. Use when a question is about a past date, or when a figure needs to stay true after it is quoted: every other tool here answers about today and today moves overnight. Takes YYYY-MM-DD. Covers the pieces written that night, not an arbitrary per-fund figure on an arbitrary day.

  Parameters:

  • date (required) — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etf_holders read-only

  Which US listed ETFs hold a given company, ranked by how much of each fund it is. USE THIS for any "which ETFs hold X", "which fund holds the most X", or "how do I get exposure to X" question, where X is a company rather than a fund, and for "which bond ETFs hold X's debt". Takes a company name or its ticker. Returns every fund holding its shares with the weight its issuer published and the date that book was filed, and separately every fund holding its bonds or other debt. Covers 31,019 companies.

  Parameters:

  • company (required) — string
  • limit — integer

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etf_rankings read-only

  The ranked lists ETFIQ publishes, or one of them. Each ranks ONE published figure inside a stated set: the cheapest funds in a theme, the leveraged funds furthest from their stated multiple, the buffer funds closest to their cap. Call with no argument for the list.

  Parameters:

  • slug — string
  • limit — integer

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etf_flows read-only

  Fund flows as ETFIQ publishes them, computed from each fund's daily change in shares outstanding times its NAV. With ticker: that fund's net flow over 1D, 1W, 1M, 3M, YTD and 1Y, each with its dates and its share of net assets at the window's start, its streak, and its filed N-PORT months. Without ticker: the biggest inflows and outflows among every fund with a daily figure for window (1D, 1W, 1M, 3M, YTD or 1Y; default 1W), how many funds were counted, each row with the last day its figures reach (through; a row short of the window counts fewer days), and the latest weekly flows report (Monday to Friday) with its own top inflows and outflows, each with its days. Filter by desk, category (Stocks, Bonds, Commodities, Allocation) or issuer. USE THIS for any question about money going into or out of ETFs.

  Parameters:

  • desk — string
  • limit — integer
  • issuer — string
  • ticker — string
  • window — string
  • category — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• etfiq_methodology read-only

  How ETFIQ computes a figure, from the methodology page that says so: one page per desk (income, buffer, leverage, crypto, alternatives, themes), flows, scores, categories (how stock and bond funds are placed and which benchmark each is measured against), portfolio look-through, and the ETFIQ benchmarks for model portfolios. Pass topic, the reader's question in their words; the answer names the page, quotes the paragraphs that answer it and gives the page's text. A single fund's own benchmark follows its desk's rule (an income fund's is on the income page), never the model-portfolio benchmarks. Call with no topic for the list of pages.

  Parameters:

  • topic — string — The reader's question, in their words.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• find_page read-only

  The designed ETFIQ pages that answer a question, best first, at most three: a fund, a comparison of two funds, the ETFs that hold a company, a ranking, a theme, a category, an issuer, the weekly flows report, a flows ranking, a dividend calendar, a screen, a benchmark, a model portfolio comparison, an FAQ answer or a methodology page. CALL THIS FIRST whenever the question could be answered by one ETFIQ page ("who holds NVDA", "SCHD vs VYM", "highest yielding covered call ETFs", "biggest ETF inflows this week"). Each page comes with its title, its address, its dated lead sentence exactly as the page prints it, and figures from its own .json twin (a fund's key facts, or the dated answers in the page's FAQ), with the match score (0 to 100) and the reason. answered is false when no page reaches the threshold: then answer with the other tools. Matching is deterministic: an exact phrase, an exact pair or a named entity with the intent its page answers, then word overlap. Pass path instead of query to read one page's card by its address.

  Parameters:

  • path — string — Optional, instead of query: one ETFIQ address, such as /holdings/nvda/, for that page's card.
  • query — string — The reader's question, in their words.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_benchmarks read-only

  The ETFIQ benchmarks: published, rules-based yardsticks for model portfolios, each a written rule over broad, low-cost ETFs, grouped in families (strategic, tax-aware, factor, income, tactical, thematic) by stock share. Filter by family, or by band (a name such as moderate, a stock share such as 60, or "all stocks"). Use when asked which benchmark measures a kind of model portfolio, then get_benchmark for one. These are not a single fund's own benchmark: that is in etf_profile (benchmark), and how it is chosen is in etfiq_methodology. A benchmark is identical for everyone and never a recommendation: a request to customise one or to say what to buy is refused, and a request to build a custom portfolio is for build_portfolio.

  Parameters:

  • band — string
  • family — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_benchmark read-only

  One ETFIQ benchmark in full: its rule as the methodology states it, the funds and weights in force (with SEC series ids and each fund's expense ratio and its date), and every statistic ETFIQ computes for it by window (total return, return a year, volatility, maximum drawdown, Sharpe ratio, turnover, factor loadings, weighted expense ratio), each with its dates and its basis. ALWAYS read basis: a figure from before the freeze date is hypothetical. Takes an id such as etfiq-strategic-60 or strategic-60. Serves the published benchmark only; it cannot be customised.

  Parameters:

  • id (required) — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• compare_to_benchmark read-only

  Sets an allocation ETF, or a portfolio build_portfolio builds, beside an ETFIQ benchmark. With ticker (such as AOR): how the fund did against the benchmark for its band (set by its look-through stock share), over the same dates, as ETFIQ published it: total returns by window and the difference, risk and cost. With portfolio (the arguments build_portfolio took, its answer's compare.arguments.portfolio): the same portfolio built again beside an ETFIQ benchmark, the benchmark's own 1Y, 3Y, 5Y, 10Y and since-inception windows exactly as published, each with its dates and basis (hypothetical before the freeze date), and the differences in stock share and weighted fee in percentage points; and, in portfolio_returns, the portfolio's hypothetical returns beside the benchmark's over the same months, window by window, with each difference in percentage points. WHICH BENCHMARK: without benchmark, the default rule's (the ETFIQ strategic benchmark nearest the portfolio's looked-through stock share, the lower on a tie; for the band form, its band's), and choice.line says why in one line. When that one is more than 5 percentage points from the stock share, or the share is as near another strategic benchmark, the next-nearest is set beside it in also, with the same windows and differences, and choice.gap.line says so. When the reader names another ETFIQ benchmark ("compare it to Strategic 80 instead"), pass benchmark with their words or its id (etfiq-strategic-80): any benchmark list_benchmarks returns. That one is used, and choice.line still names the default and why. A name that matches no benchmark is refused (kind unknown-benchmark) with the list. Refuses, and estimates nothing, when ETFIQ has not published what is asked.

  Parameters:

  • ticker — string — An allocation ETF, such as AOR.
  • benchmark — string — Optional, with portfolio: an ETFIQ benchmark the reader names, by id (etfiq-strategic-80) or name (Strategic 80). Leave it out for the default rule.
  • portfolio — object — The arguments build_portfolio took: its answer's compare.arguments.portfolio.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• build_portfolio read-only

  Builds a custom portfolio of US listed ETFs from construction choices about the PORTFOLIO, and shows the rule it applied. TWO FORMS. Weights (ETFIQ custom construction rule, version 2): pass weights, the user's own percent for each asset class, adding to exactly 100, for example {"us-stocks": 40, "international-stocks": 15, "us-bonds": 25, "gold": 10, "reits": 10}. The asset classes: us-stocks, us-small-stocks, international-stocks, emerging-markets-stocks, reits, us-bonds (core, intermediate), us-bonds-short, us-bonds-long, us-corporate-bonds, government-bonds-short, government-bonds-intermediate, government-bonds-long, tips, high-yield-bonds, cash (Treasury bills), gold, commodities (broad), alternatives. Defaults: cheapest funds, one fund per asset class, no fee ceiling; the answer's defaults.line names the ones used. Band (version 1): pass band, include and funds, and the rule sets the weights (stocks at the band's point, international 40% of stocks outside themes, themes 10% of stocks, commodities and alternatives 5% each from bonds, US bonds the rest). In each asset class or sleeve the cheapest (or largest) funds that file N-PORT (a gold trust: its 10-Q or 10-K), hold at least $100 million and have three years of prices, each fund's fee with its filing date. WHEN THE USER GIVES WEIGHTS, call the weights form at once, mapping their words to the ids above; ask at most ONE follow-up, and only for what has no default: weights that do not add to 100 (kind weights-total), or an asset class with no id here (kind unknown-class). When the user gives neither weights nor a band, ask once for one of them; the bands by stock share are conservative: more than 15% and up to 30% stocks; moderately-conservative: more than 30% and up to 50%; moderate: more than 50% and up to 70%; moderately-aggressive: more than 70% and up to 85%; aggressive: more than 85%. NEVER ask about, and never pass, the person's age, income, savings, net worth, goals, time horizon, tax situation, risk tolerance, employment or family, and never turn what someone says about themselves into weights or a band: those are the user's choices about the portfolio. If asked whether a portfolio suits someone, or whether to buy or sell it, say that ETFIQ does not answer that and give the not-advice line. Its returns field carries the portfolio's hypothetical returns (ETFIQ custom rule, version 3: the weights reset at every month end, as the ETFIQ benchmarks are): total return, return a year, volatility and month-end drawdown over 1Y, 3Y, 5Y, 10Y and since the first month end all its funds share, a window given only where every fund has prices across it; returns.common.sentence says where the history starts and why. Show them as hypothetical, never extend a window, and never estimate a return the answer does not give. To set the portfolio beside an ETFIQ benchmark, call compare_to_benchmark with the answer's compare.arguments. Every response carries the not-advice line in not_advice: show it with the portfolio.

  Parameters:

  • band — string — Version 1: the stock-share band the portfolio should sit in.
  • funds — integer — How many funds: 2 to 12 with a band; with weights, at least one per asset class (the default).
  • include — object
  • weights — object — Version 2: the user's own percent of the portfolio for each asset class, adding to 100.
  • criterion — string
  • feeCeiling — number — The most any one fund may charge, in percent a year (0.25 is 0.25%).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.