# VistaShares ETFs (remote · www.vistashares.com)

Official read-only VistaShares ETF data and calculators: fund facts, holdings, distributions, FAQs.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.vistashares.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-vistashares-etfs/www.md), [page](https://verifymcp.io/servers/com-vistashares-etfs/www)

## Channel facts

- Endpoint: `https://www.vistashares.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1843 tokens (~122/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the VistaShares ETFs MCP server?

VistaShares ETFs is a hosted endpoint at https://www.vistashares.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-vistashares-etfs 'https://www.vistashares.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-vistashares-etfs": {
      "url": "https://www.vistashares.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-vistashares-etfs": {
      "type": "http",
      "url": "https://www.vistashares.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-vistashares-etfs]
url = "https://www.vistashares.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-vistashares-etfs": {
      "type": "remote",
      "url": "https://www.vistashares.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-vistashares-etfs --url 'https://www.vistashares.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-vistashares-etfs:
    url: "https://www.vistashares.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-vistashares-etfs": {
      "Transport": "http",
      "Url": "https://www.vistashares.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-vistashares-etfs -t streamable-http -u 'https://www.vistashares.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-vistashares-etfs": {
      "type": "http",
      "url": "https://www.vistashares.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 70, 0)

- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool “ai_supply_chain_layers” now declares an output schema
- [functional improvement] Tool “buffer_mid_period” now declares an output schema
- [functional improvement] Tool “buffer_options_builder” now declares an output schema
- [functional improvement] Tool “buffer_outcome” now declares an output schema
- [functional improvement] Tool “buffer_payoff_table” now declares an output schema
- [functional improvement] Tool “covered_call_outcome” now declares an output schema
- [functional improvement] Tool “etf_cost” now declares an output schema
- [functional improvement] Tool “get_distributions” now declares an output schema
- [functional improvement] Tool “get_documents” now declares an output schema
- [functional improvement] Tool “get_fund” now declares an output schema
- [functional improvement] Tool “get_holdings” now declares an output schema
- [functional improvement] Tool “list_funds” now declares an output schema
- [functional improvement] Tool “loss_recovery” now declares an output schema
- [functional improvement] Tool “search_faq” now declares an output schema
- [functional improvement] Tool “supercycle_spending” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Server version: 1.1.0 → 1.3.0
- [cosmetic] “buffer_mid_period” reworded the description of “buffer_pct”
- [cosmetic] “buffer_mid_period” reworded the description of “cap_pct”
- [cosmetic] “buffer_mid_period” reworded the description of “fund_change_pct”
- [cosmetic] “buffer_mid_period” reworded the description of “index_change_pct”
- [cosmetic] “buffer_outcome” reworded the description of “buffer_pct”
- [cosmetic] “buffer_outcome” reworded the description of “cap_pct”
- [cosmetic] “buffer_outcome” reworded the description of “index_return_pct”
- [cosmetic] “buffer_payoff_table” reworded the description of “buffer_pct”
- [cosmetic] “buffer_payoff_table” reworded the description of “cap_pct”
- [cosmetic] “search_faq” reworded the description of “query”
- [cosmetic] “buffer_payoff_table” reworded the description of “loss_share_beyond_buffer”
- [cosmetic] “covered_call_outcome” reworded the description of “premium_pct”
- [cosmetic] “covered_call_outcome” reworded the description of “stock_return_pct”
- [cosmetic] “covered_call_outcome” reworded the description of “strike_pct”
- [cosmetic] “etf_cost” reworded the description of “amount”
- [cosmetic] “etf_cost” reworded the description of “expense_ratio_pct”
- [cosmetic] “etf_cost” reworded the description of “spread_pct”
- [cosmetic] “etf_cost” reworded the description of “years”
- [cosmetic] “get_distributions” reworded the description of “ticker”
- [cosmetic] “get_documents” reworded the description of “ticker”
- [cosmetic] “get_fund” reworded the description of “ticker”
- [cosmetic] “get_holdings” reworded the description of “ticker”
- [cosmetic] “list_funds” reworded the description of “family”
- [cosmetic] “loss_recovery” reworded the description of “loss_pct”
- [cosmetic] “search_faq” reworded the description of “limit”
- [cosmetic] “search_faq” reworded the description of “ticker”
- [cosmetic] “supercycle_spending” reworded the description of “cycle”
- [cosmetic] “loss_recovery” made “loss_pct” optional

### 2026-11-15 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 69)

First indexed and scored.

## MCP tools (15)

### `list_funds` (~92 tokens)

List VistaShares ETFs

Lists all 13 VistaShares ETFs with ticker, name, family, exchange, CUSIP, inception date, expense ratio, net assets (with as-of date), description and key document links. Optional family filter.

Input parameters:

- `family` (string): Optional family filter: target-15 (covered call), supercycle (thematic infrastructure) or shield (monthly buffer). Omit to list all 13 funds.

Output parameters:

- `disclosure` (string): Disclosure to show with the data.
- `funds` (array)

### `get_fund` (~96 tokens)

Get fund facts

Key facts for one VistaShares ETF as published on its fund page, each with its as-of date: objective, CUSIP, exchange, inception date, expense ratio, net assets, shares outstanding, number of holdings, distribution frequency, holdings, distributions and documents.

Input parameters:

- `ticker` (string, required): Fund ticker, one of the 13 VistaShares ETFs listed in the enum (for example OMAH, AIS or VOOB).

Output parameters:

- `cusip` (string)
- `data_url` (string)
- `description` (string)
- `disclosure` (string): Disclosure to show with the data.
- `distribution_frequency` (string)
- `distributions` (object)
- `documents` (array)
- `exchange` (string)
- `expense_ratio` (string)
- `facts` (object): Every fact on the fund page, keyed by its label.
- `family` (string)
- `family_url` (string)
- `fund_page` (string)
- `holdings` (object)
- `inception_date` (string)
- `key_documents` (object)
- `name` (string)
- `net_assets` (string)
- `net_assets_as_of` (string|null)
- `number_of_holdings` (string)
- `number_of_holdings_as_of` (string|null)
- `objective` (string|null)
- `retrieved_at` (string|null)
- `summary` (string|null)
- `ticker` (string)

### `get_holdings` (~70 tokens)

Get holdings

Holdings of a VistaShares ETF as published on its fund page (name, ticker, market value and weight), with the as-of date.

Input parameters:

- `ticker` (string, required): Fund ticker, one of the 13 VistaShares ETFs listed in the enum (for example OMAH, AIS or VOOB).

Output parameters:

- `disclosure` (string): Disclosure to show with the data.
- `fund_page` (string)
- `holdings` (object)
- `ticker` (string)

### `get_distributions` (~81 tokens)

Get distribution calendar

Distribution calendar and history of a VistaShares ETF (declaration, ex, record and payable dates and per-share amounts) as published on the fund page. Funds without distributions return an empty list.

Input parameters:

- `ticker` (string, required): Fund ticker, one of the 13 VistaShares ETFs listed in the enum (for example OMAH, AIS or VOOB).

Output parameters:

- `disclosure` (string): Disclosure to show with the data.
- `distribution_frequency` (string|null)
- `distributions` (array)
- `fund_page` (string)
- `ticker` (string)

### `get_documents` (~71 tokens)

Get fund documents

Links to the prospectus, summary prospectus, SAI, fact sheet, reports and Section 19(a) notices for a VistaShares ETF.

Input parameters:

- `ticker` (string, required): Fund ticker, one of the 13 VistaShares ETFs listed in the enum (for example OMAH, AIS or VOOB).

Output parameters:

- `disclosure` (string): Disclosure to show with the data.
- `documents` (array)
- `fund_page` (string)
- `ticker` (string)

### `search_faq` (~122 tokens)

Search VistaShares FAQs

Searches the published VistaShares FAQs (fund pages, fund family pages and About) and returns matching questions and answers with their source page.

Input parameters:

- `limit` (integer): Maximum number of results to return. Accepts 1 to 10; default 5.
- `query` (string, required): Question or keywords, for example "When does OMAH pay distributions?". Required; words of three letters or fewer are ignored.
- `ticker` (string): Optional: search only this fund's FAQs. Omit to search every fund page plus the family and About pages.

Output parameters:

- `disclosure` (string): Disclosure to show with the data.
- `results` (array)

### `covered_call_outcome` (~149 tokens)

Covered call outcome calculator

Shows what a covered call position returns for a given stock move, call strike and option premium, compared with owning the stocks alone. Same math as https://www.vistashares.com/covered-call-calculator/.

Input parameters:

- `premium_pct` (number): Option premium received, in percent of the position. Accepts 0 to 50; default 2.
- `stock_return_pct` (number): Stock return over the option period, in percent (for example 8 or -12). Accepts -100 to 200; default 8.
- `strike_pct` (number): Call strike, in percent above the current price. Accepts 0 to 100; default 5.

Output parameters:

- `covered_call` (string)
- `explanation` (string)
- `inputs` (object)
- `note` (string)
- `page` (string)
- `stocks_alone` (string)

### `buffer_outcome` (~134 tokens)

Buffer ETF outcome calculator

Shows the outcome of a buffered position for a given index return, buffer size and cap over one outcome period. Same math as https://www.vistashares.com/buffer-etf-calculator/.

Input parameters:

- `buffer_pct` (number): Buffer size, in percent of losses absorbed first. Accepts 0 to 100; default 10.
- `cap_pct` (number): Cap on gains, in percent. Accepts 0 to 200; default 12.
- `index_return_pct` (number): Index return over the outcome period, in percent. Accepts -100 to 200; default -15.

Output parameters:

- `buffered` (string)
- `explanation` (string)
- `index` (string)
- `inputs` (object)
- `note` (string)
- `page` (string)

### `buffer_payoff_table` (~157 tokens)

Buffer ETF payoff table

Returns the payoff of a buffered position across index returns from -40% to +30%, for a chosen buffer, cap and share of losses kept beyond the buffer. Same math as https://www.vistashares.com/buffer-etf-payoff-chart/.

Input parameters:

- `buffer_pct` (number): Buffer size, in percent. Accepts 0 to 100; default 10.
- `cap_pct` (number): Cap on gains, in percent. Accepts 0 to 200; default 12.
- `loss_share_beyond_buffer` (number): Share of losses beyond the buffer that the investor bears (1 = all, 0.5 = half). Accepts 0 to 1; default 1.

Output parameters:

- `inputs` (object)
- `note` (string)
- `page` (string)
- `payoff` (array)

### `buffer_options_builder` (~71 tokens)

How a buffer is built from options

Explains, step by step, how owning an index plus buying a put, selling a lower put and selling a call creates a buffered payoff (10% buffer, 12% cap example), with payoff values for each step. Same content as https://www.vistashares.com/buffer-options-builder/.

Output parameters:

- `example` (string)
- `note` (string)
- `page` (string)
- `steps` (array)

### `buffer_mid_period` (~195 tokens)

Buffer ETF mid-period calculator

For someone buying a buffer ETF partway through its outcome period: remaining upside to the cap, how far the index must fall before the buffer starts, and how much buffer is left, given the index and fund moves since the period began. Same math as https://www.vistashares.com/buffer-etf-mid-period-calculator/.

Input parameters:

- `buffer_pct` (number): Buffer size for the full period, in percent. Accepts 0 to 100; default 10.
- `cap_pct` (number): Cap for the full period, in percent. Accepts 0 to 200; default 12.
- `fund_change_pct` (number): Fund value change since the period started, in percent. Accepts -90 to 200; default 3.
- `index_change_pct` (number): Index change since the period started, in percent. Accepts -90 to 200; default 5.

Output parameters:

- `buffer_remaining` (string)
- `decline_before_buffer_starts` (string)
- `explanation` (string)
- `inputs` (object)
- `note` (string)
- `page` (string)
- `payoff_for_buyer_today` (array)
- `remaining_upside` (string)

### `loss_recovery` (~93 tokens)

Loss recovery calculator

Shows the gain needed to recover from a given loss (a 50% loss needs a 100% gain), and what $100,000 becomes after the loss. Same math as https://www.vistashares.com/loss-recovery-calculator/.

Input parameters:

- `loss_pct` (number): Loss, in percent (positive number, for example 30). Accepts 0 to 99; default 30.

Output parameters:

- `explanation` (string)
- `gain_needed_to_recover` (string)
- `loss` (string)
- `note` (string)
- `page` (string)
- `value_of_100000_after_loss` (string)

### `etf_cost` (~168 tokens)

ETF cost calculator

Estimates the dollar cost of holding an ETF: expense ratio over a holding period plus the bid-ask spread paid when buying and later selling. Same math as https://www.vistashares.com/etf-cost-calculator/.

Input parameters:

- `amount` (number): Amount invested, in dollars. Accepts 0 to 1000000000; default 100000.
- `expense_ratio_pct` (number): Expense ratio, in percent per year. Accepts 0 to 5; default 0.5.
- `spread_pct` (number): Round-trip bid-ask spread, in percent. Accepts 0 to 5; default 0.1.
- `years` (number): Holding period, in years. Accepts 1 to 50; default 5.

Output parameters:

- `expense_ratio_cost` (string)
- `explanation` (string)
- `inputs` (object)
- `note` (string)
- `page` (string)
- `spread_cost` (string)
- `total_cost` (string)

### `supercycle_spending` (~115 tokens)

Supercycle spending breakdown

Where the money goes in five infrastructure buildouts: a 1 GW AI data center, global power sector investment, the U.S. defense budget request, the global space economy and a humanoid robot bill of materials. Each row has a value, share and description, with the cited source. Same data as https://www.vistashares.com/supercycle-spending-breakdown/.

Input parameters:

- `cycle` (string): Which breakdown to return: ai, power, defense, space or robotics. Omit for all five.

Output parameters:

- `breakdowns` (array)
- `note` (string)
- `page` (string)

### `ai_supply_chain_layers` (~64 tokens)

AI supply chain map

The six layers of the AI supply chain (chips, memory, networking, servers, data centers, power and grid), each with a short description and a VistaShares guide link. Same content as https://www.vistashares.com/ai-supply-chain-map/.

Output parameters:

- `layers` (array)
- `page` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-vistashares-etfs/www#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 71
- 2026-11-17: 71
- 2026-11-16: 70
- 2026-11-15: 70
- 2026-11-14: 69

## Common questions

### What is the VistaShares ETFs MCP server?

VistaShares ETFs is an MCP server listed in the public MCP registry as com.vistashares/etfs. Official read-only VistaShares ETF data and calculators: fund facts, holdings, distributions, FAQs. This page covers its hosted endpoint (https://www.vistashares.com/mcp).

### Is the VistaShares ETFs MCP server safe to use?

VistaShares ETFs scores 72 out of 100 on VerifyMCP. 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 VistaShares ETFs MCP server expose?

VistaShares ETFs exposes 15 tools: list_funds, get_fund, get_holdings, get_distributions, get_documents, and 10 more. Their descriptions and schemas cost roughly 1,678 tokens of context every time the server is loaded.

### Does the VistaShares ETFs MCP server require authentication?

No. We connected to VistaShares ETFs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the VistaShares ETFs MCP server still maintained?

VistaShares ETFs is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the VistaShares ETFs MCP server?

VerifyMCP ran 13 checks on VistaShares ETFs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.vistashares.com/mcp
- Website: https://www.vistashares.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-vistashares-etfs/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-vistashares-etfs/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-vistashares-etfs/www.json
- HTML version of this page: https://verifymcp.io/servers/com-vistashares-etfs/www
