Index Constituents
NPM · @PIPEWORX/MCP-INDEX-CONSTITUENTS · 2 COMPONENTS
Index constituents and holdings, point-in-time.
Available components
Last scanned (13 hours ago)
Scores higher than 72% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-index-constituents). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 790 tokens (~263/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.10 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-index-constituents@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-index-constituents |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-index-constituents/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637427249 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e64fc93109084d588e9f6fbe50b1166bc3adbad9c97b1e57037dd00d93e6e8e229c45456378942e8ce053f4d4e4ca724396cac4673bcdcf4083b958d8 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
constituent_changes ~234
Dated additions and removals from the S&P 500, sourced from Wikipedia's maintained "Historical components of the S&P 500" table (every S&P-announced swap since 1963, each with its effective date, the ticker/company added, the ticker/company removed, and the stated reason). Answers "what changed in the S&P 500 in 2024", "when was X removed from the S&P 500 and what replaced it". Only sp500 is covered — the iShares-backed indexes above have no equivalent public, dated changes table.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Earliest effective date to include, as a year ("2024") or ISO date ("2024-01-01"). Omit for no lower bound. |
| index | string | yes | Only "sp500" is supported. |
| limit | number | – | Max rows to return, most recent first (default 50, max 600). |
| to | string | – | Latest effective date to include, as a year ("2024") or ISO date ("2024-12-31"). Omit for no upper bound. |
No output schema declared.
No examples provided.
index_constituents ~256
Current constituents of a major US or developed-markets equity index — ticker, name, GICS sector, and weight — sourced from the matching iShares index-tracking ETF's daily holdings file (the closest free, point-in-time proxy for official index membership and weights; S&P/Russell do not publish those for free). Answers "what's in the S&P 500 right now", "top holdings of the Russell 2000 by weight", "which sectors make up the S&P MidCap 400". Cash, collateral and futures positions the ETF holds are excluded here — use ishares_etf_holdings for those.
| Name | Type | Req | Description |
|---|---|---|---|
| index | string | yes | Which index. One of: sp500, sp400, sp600, russell1000, russell2000, eafe. |
| limit | number | – | Max rows to return, sorted by weight descending (default 50, max 600 — pass the max to get the full index in one call). |
| offset | number | – | Rows to skip, for paging past `limit` (default 0). |
| sector | string | – | Optional GICS sector filter, case-insensitive substring match (e.g. "Health Care", "Energy"). |
No output schema declared.
No examples provided.
ishares_etf_holdings ~242
Full reported holdings of one of six iShares index-tracking ETFs (IVV, IJH, IJR, IWB, IWM, EFA) as of the fund's own "as of" date — every position including cash, collateral and futures, each labeled with its asset class so they are never silently mixed in with equities. Answers "what does IVV actually hold today", "how much cash does this ETF carry". For just the equity index membership, use index_constituents instead.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_class | string | – | Optional filter, case-insensitive exact match against the fund's own asset-class label (e.g. "Equity", "Cash", "Futures", "Cash Collateral and Margins", "Money Market"). |
| limit | number | – | Max rows to return, sorted by market value descending (default 50, max 600). |
| offset | number | – | Rows to skip, for paging past `limit` (default 0). |
| ticker | string | yes | One of the supported iShares ETFs: IVV, IJH, IJR, IWB, IWM, EFA. |
No output schema declared.
No examples provided.
How do I install the Index Constituents MCP server?
Index Constituents runs locally as an npm package, launched with npx -y @pipeworx/mcp-index-constituents. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-index-constituents
claude mcp add pipeworx-io-index-constituents -- npx -y @pipeworx/mcp-index-constituents
What is the Index Constituents MCP server?
Index Constituents is an MCP server listed in the public MCP registry as io.github.pipeworx-io/index-constituents. Index constituents and holdings, point-in-time. This page covers its npm package (@pipeworx/mcp-index-constituents).
Is the Index Constituents MCP server safe to use?
Index Constituents scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Index Constituents MCP server expose?
Index Constituents exposes 3 tools: index_constituents, ishares_etf_holdings, constituent_changes. Their descriptions and schemas cost roughly 732 tokens of context every time the server is loaded.
Is the Index Constituents MCP server still maintained?
Index Constituents is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Index Constituents MCP server under?
Index Constituents declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.