Morningstar Fund & ETF Scraper | Ratings, Fees | from $2/1K

For portfolio trackers, fund-comparison tools, and AI agents that need structured mutual fund and ETF data — without a Morningstar Premium subscription.

No API key required. No Morningstar account. Pay per fund record (Pay Per Event). Every record includes parseConfidence (0.0–1.0) and warnings.

Scrape mutual fund and ETF data from Morningstar by ticker symbol — category, star rating, expense ratios, fund size, NAV, distribution yield, turnover, manager tenure, style box, and fund company, all in one call. No login, no proxy setup (Apify Residential proxy is wired in by default). Pay per result.

---

What data you get

One record per ticker with:

• fundName, category, broadCategoryGroup, styleBox
• starRating — Morningstar's 1–5 star rating
• expenseRatio (adjusted), netExpenseRatio
• netAssetsUsd — fund size in raw USD (not rounded to billions)
• nav, navChangePct — latest net asset value + most recent daily change
• distributionYield, turnoverRatio, minimumInvestment
• investmentStatus (Open/Closed), shareClassType
• longestManagerTenureYears
• amcName — the fund's asset management company
• morningstarUrl — canonical fund page

All records include parseConfidence and warnings.

Known gap — trailing & YTD returns

return1Year, return3Year, return5Year, and returnYtd are declared in the schema but always ship as null with a "returns_subscription_locked" warning. Morningstar puts trailing and year-to-date performance figures behind a paid subscription on every public surface we tested (the public search API, the fund page's own embedded data, and the legacy quote/performance APIs, tried both keyless and with a page-issued auth token). If you need those figures, Morningstar Premium is currently the only reliable source. Everything else in this actor comes from Morningstar's genuinely free public pages.

---

How to use

Look up a handful of funds

{
  "tickers": ["WFILX", "VTSAX", "FXAIX"]
}

Screen a larger watchlist

{
  "tickers": ["SPY", "QQQ", "VTI", "SWPPX", "FSKAX", "SCHB"],
  "maxItems": 50
}

---

Input parameters

Field	Type	Default	Description
tickers	string[]	required	Fund/ETF ticker symbols, e.g. ["WFILX", "VTSAX", "SPY"]
proxyConfiguration	object	RESIDENTIAL	Apify proxy used to reach Morningstar
maxItems	integer	100	Cap on tickers processed (0 = no limit)

---

Output schema

Field	Type
ticker	string
fundName	string
category	string
broadCategoryGroup	string
starRating	integer (1–5)
expenseRatio / netExpenseRatio	float %
netAssetsUsd	float
nav / navChangePct	float
distributionYield	float %
turnoverRatio	float %
minimumInvestment	float
investmentStatus	string
shareClassType	string
styleBox	string
longestManagerTenureYears	float
amcName	string
morningstarUrl	string
return1Year / return3Year / return5Year / returnYtd	float (always null — see Known gap)
scrapedAt	string
parseConfidence	float
warnings	array

---

Sample record

{
  "ticker": "FXAIX",
  "fundName": "Fidelity 500 Index Fund",
  "category": "Large Blend",
  "broadCategoryGroup": "Equity",
  "starRating": 4,
  "expenseRatio": 0.015,
  "netExpenseRatio": 0.01,
  "netAssetsUsd": 827509261845.0,
  "nav": 258.7,
  "navChangePct": -0.18905,
  "distributionYield": 1.04085,
  "turnoverRatio": 3.0,
  "minimumInvestment": 0.0,
  "investmentStatus": "Open",
  "shareClassType": "No Load",
  "styleBox": "Large Blend",
  "longestManagerTenureYears": 17.47,
  "amcName": "Fidelity",
  "morningstarUrl": "https://www.morningstar.com/funds/xnas/fxaix/quote",
  "return1Year": null,
  "return3Year": null,
  "return5Year": null,
  "returnYtd": null,
  "scrapedAt": "2026-07-21T05:47:50Z",
  "parseConfidence": 0.8,
  "warnings": ["returns_subscription_locked"]
}

---

Use with AI agents (MCP)

This actor is callable as a tool by AI agents (Claude Desktop, Cursor, VS Code, n8n, LangGraph, CrewAI, or any MCP-compatible client) via Apify's hosted Model Context Protocol server — e.g. "what's the expense ratio and star rating on VTSAX?".

{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.apify.com/?tools=bovi/morningstar-fund-screener",
        "--header",
        "Authorization: Bearer <YOUR_APIFY_TOKEN>"
      ]
    }
  }
}

---

FAQ

Does it need a Morningstar account or subscription? No. Every field this actor returns comes from Morningstar's public pages. Trailing/YTD returns are the one thing Morningstar keeps behind Premium — see "Known gap" above.

Why is navChangePct sometimes null? It reflects Morningstar's most recent NAV update; it isn't always populated for every fund at every point in the trading day.

Is netAssetsUsd in dollars or billions? Raw USD (e.g. 1521430094 = $1.52B) — no rounding, so you can do your own math without a unit-conversion step.

Legal

Not affiliated with Morningstar, Inc. This actor uses publicly accessible pages. Use responsibly.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.