
Index Constituents MCP server
online · 100% uptimeIndex constituents and holdings, point-in-time.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Index Constituents yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Index Constituents tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Index Constituents compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 108 ms
- faster than 82% of 30,031 servers
Release history: 4 versions in the registry since 2026-10-13, latest 2026-11-02, typically one every 3 days.
Install Index Constituents in Claude Code, Cursor or VS Code
claude mcp add --transport http index-constituents https://gateway.pipeworx.io/index-constituents/mcp
What the publisher says
From the Index Constituents repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/index-constituents
Current constituents, weights and sectors of six major US and developed-markets equity indexes, plus a dated history of S&P 500 additions and removals — point-in-time index membership built from a live ETF proxy, not a licensed index feed.
Part of Pipeworx — an MCP gateway connecting AI agents to 1779+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
constituents of one index (sp500, sp400, sp600, russell1000, russell2000, eafe): ticker, name, GICS sector, weight, and the fund's "as of" date. Sorted by weight descending. Cash/collateral/futures the tracking ETF also holds are excluded here (see isharesetfholdings). Default limit is 50; pass limit: 600 (the max) to get the whole index in one call — a ~503-row S&P 500 answer is available on request, not by default.
- index_constituents(index, limit?, offset?, sector?) — current equity
position of one of the six tracking ETFs (IVV, IJH, IJR, IWB, IWM, EFA), including cash, collateral and futures, each labeled with its own asset_class so they are never silently folded in with equities.
- isharesetfholdings(ticker, limit?, offset?, asset_class?) — every reported
removes (index must be sp500; the other five indexes have no public, dated changes table). from/to accept a bare year ("2024") or an ISO date.
- constituent_changes(index, from?, to?, limit?) — dated S&P 500 adds and
Auth
Keyless. Both upstreams are public, unauthenticated pages.
Data sources
own index-tracking ETF (IVV/S&P 500, IJH/S&P MidCap 400, IJR/S&P SmallCap 600, IWB/Russell 1000, IWM/Russell 2000, EFA/MSCI EAFE). This is a PROXY for official index membership, not the index provider's own data: S&P and Russell do not publish their constituent files for free, so the fund's actual reported portfolio — which tracks its index closely — is the nearest public point-in-time stand-in. Weights are the ETF's own portfolio weights, not S&P/Russell's published index weights, and can differ slightly (cash drag, sampling, corporate-action timing).
- iShares (BlackRock) — the daily holdings file each fund publishes for its
S&P 500" (the latter is this pack's source for constituent_changes: a community-maintained, citation-backed table of every S&P-announced S&P 500 swap since 1963, with its effective date and stated reason).
- Wikipedia — "List of S&P 500 companies" and "Historical components of the
Reuse note (checked 2026-10-12). BlackRock's site terms (blackrock.com/corporate/compliance/terms-and-conditions) say website content is "solely for your personal, non-commercial use" and may not be "distribute[d], modif[ied], transmit[ted], reuse[d], repost[ed]... for public or commercial purposes... without BlackRock's written permission." This pack does not store, mirror or redistribute the holdings file: every call fetches the fund's current file live (cached at the edge for a day, the same way a normal browser would cache it) and returns the parsed rows for that one call. Per the proxy-vs-mirror rule (CLAUDE.md, fleet #1389 — "a live upstream call per request needs no explicit grant; only bulk-copying/mirroring does"), that is proxying, not redistribution; no dataset is baked into this pack or into Pipeworx's own storage. Wikipedia's content is CC BY-SA 4.0, which permits reuse including attribution-carrying commercial reuse — source on every response names Wikipedia and the page.
Notes
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Index Constituents: common questions
- Is Index Constituents MCP server safe?
- Mostly: it is graded B (77/100). Read the Index Constituents safety report
- How do I install Index Constituents?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Index Constituents need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Index Constituents maintained?
- The last commit was 22 days ago (2026-10-13). The latest release is v0.2.1.
- Is Index Constituents up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Index Constituents compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 108 ms (faster than 82% of 30,031 servers). Full comparison.