Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VistaShares ETFs

REMOTE · WWW.VISTASHARES.COM

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

+3 this week 72 Trust /100

Last scanned (17 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 16 Nov 26 0
    • Schema quality: pass → fail ▼ functional
    • Tool “ai_supply_chain_layers” now declares an output schema ▲ functional
    • Tool “buffer_mid_period” now declares an output schema ▲ functional
    • Tool “buffer_options_builder” now declares an output schema ▲ functional
    • Tool “buffer_outcome” now declares an output schema ▲ functional
    • Tool “buffer_payoff_table” now declares an output schema ▲ functional
    • Tool “covered_call_outcome” now declares an output schema ▲ functional
    • Tool “etf_cost” now declares an output schema ▲ functional
    • Tool “get_distributions” now declares an output schema ▲ functional
    • Tool “get_documents” now declares an output schema ▲ functional
    • Tool “get_fund” now declares an output schema ▲ functional
    • Tool “get_holdings” now declares an output schema ▲ functional
    • Tool “list_funds” now declares an output schema ▲ functional
    • Tool “loss_recovery” now declares an output schema ▲ functional
    • Tool “search_faq” now declares an output schema ▲ functional
    • Tool “supercycle_spending” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Server version: 1.1.0 → 1.3.0 functional
    • “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 cosmetic
  • 15 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 69

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://www.vistashares.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vistashares.com CN=YE1,O=Let's Encrypt,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA384 634df1baa856c34f75e063811829a3195ea
SANs: *.vistashares.com, vistashares.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.vistashares.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
vistashares.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
referrer-policy no-referrer-when-downgrade

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.vistashares.com/mcp Verified 200
http (plaintext) http://www.vistashares.com/mcp HTTPS enforced 301 https://www.vistashares.com/mcp
MCP tools · 15 exposed · ~1,678 tokens

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 →

Tool Tokens
ai_supply_chain_layers ~64

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/.

Input schema present but exposes no named parameters.

NameTypeReqDescription
layersarrayyes–
pagestringyes–

No examples provided.

buffer_mid_period ~195

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/.

NameTypeReqDescription
buffer_pctnumber–Buffer size for the full period, in percent. Accepts 0 to 100; default 10.
cap_pctnumber–Cap for the full period, in percent. Accepts 0 to 200; default 12.
fund_change_pctnumber–Fund value change since the period started, in percent. Accepts -90 to 200; default 3.
index_change_pctnumber–Index change since the period started, in percent. Accepts -90 to 200; default 5.
NameTypeReqDescription
buffer_remainingstringyes–
decline_before_buffer_startsstringyes–
explanationstringyes–
inputsobjectyes–
notestringyes–
pagestringyes–
payoff_for_buyer_todayarrayyes–
remaining_upsidestringyes–

No examples provided.

buffer_options_builder ~71

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/.

Input schema present but exposes no named parameters.

NameTypeReqDescription
examplestringyes–
notestringyes–
pagestringyes–
stepsarrayyes–

No examples provided.

buffer_outcome ~134

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/.

NameTypeReqDescription
buffer_pctnumber–Buffer size, in percent of losses absorbed first. Accepts 0 to 100; default 10.
cap_pctnumber–Cap on gains, in percent. Accepts 0 to 200; default 12.
index_return_pctnumber–Index return over the outcome period, in percent. Accepts -100 to 200; default -15.
NameTypeReqDescription
bufferedstringyes–
explanationstringyes–
indexstringyes–
inputsobjectyes–
notestringyes–
pagestringyes–

No examples provided.

buffer_payoff_table ~157

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/.

NameTypeReqDescription
buffer_pctnumber–Buffer size, in percent. Accepts 0 to 100; default 10.
cap_pctnumber–Cap on gains, in percent. Accepts 0 to 200; default 12.
loss_share_beyond_buffernumber–Share of losses beyond the buffer that the investor bears (1 = all, 0.5 = half). Accepts 0 to 1; default 1.
NameTypeReqDescription
inputsobjectyes–
notestringyes–
pagestringyes–
payoffarrayyes–

No examples provided.

covered_call_outcome ~149

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/.

NameTypeReqDescription
premium_pctnumber–Option premium received, in percent of the position. Accepts 0 to 50; default 2.
stock_return_pctnumber–Stock return over the option period, in percent (for example 8 or -12). Accepts -100 to 200; default 8.
strike_pctnumber–Call strike, in percent above the current price. Accepts 0 to 100; default 5.
NameTypeReqDescription
covered_callstringyes–
explanationstringyes–
inputsobjectyes–
notestringyes–
pagestringyes–
stocks_alonestringyes–

No examples provided.

etf_cost ~168

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/.

NameTypeReqDescription
amountnumber–Amount invested, in dollars. Accepts 0 to 1000000000; default 100000.
expense_ratio_pctnumber–Expense ratio, in percent per year. Accepts 0 to 5; default 0.5.
spread_pctnumber–Round-trip bid-ask spread, in percent. Accepts 0 to 5; default 0.1.
yearsnumber–Holding period, in years. Accepts 1 to 50; default 5.
NameTypeReqDescription
expense_ratio_coststringyes–
explanationstringyes–
inputsobjectyes–
notestringyes–
pagestringyes–
spread_coststringyes–
total_coststringyes–

No examples provided.

get_distributions ~81

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.

NameTypeReqDescription
tickerstringyesFund ticker, one of the 13 VistaShares ETFs listed in the enum (for example OMAH, AIS or VOOB).
NameTypeReqDescription
disclosurestringyesDisclosure to show with the data.
distribution_frequencystring|nullyes–
distributionsarrayyes–
fund_pagestringyes–
tickerstringyes–

No examples provided.

get_documents ~71

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

NameTypeReqDescription
tickerstringyesFund ticker, one of the 13 VistaShares ETFs listed in the enum (for example OMAH, AIS or VOOB).
NameTypeReqDescription
disclosurestringyesDisclosure to show with the data.
documentsarrayyes–
fund_pagestringyes–
tickerstringyes–

No examples provided.

get_fund ~96

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.

NameTypeReqDescription
tickerstringyesFund ticker, one of the 13 VistaShares ETFs listed in the enum (for example OMAH, AIS or VOOB).
NameTypeReqDescription
cusipstring––
data_urlstringyes–
descriptionstringyes–
disclosurestringyesDisclosure to show with the data.
distribution_frequencystring––
distributionsobjectyes–
documentsarrayyes–
exchangestringyes–
expense_ratiostring––
factsobjectyesEvery fact on the fund page, keyed by its label.
familystringyes–
family_urlstringyes–
fund_pagestringyes–
holdingsobjectyes–
inception_datestring––
key_documentsobjectyes–
namestringyes–
net_assetsstring––
net_assets_as_ofstring|null––
number_of_holdingsstring––
number_of_holdings_as_ofstring|null––
objectivestring|nullyes–
retrieved_atstring|nullyes–
summarystring|nullyes–
tickerstringyes–

No examples provided.

get_holdings ~70

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

NameTypeReqDescription
tickerstringyesFund ticker, one of the 13 VistaShares ETFs listed in the enum (for example OMAH, AIS or VOOB).
NameTypeReqDescription
disclosurestringyesDisclosure to show with the data.
fund_pagestringyes–
holdingsobjectyes–
tickerstringyes–

No examples provided.

list_funds ~92

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.

NameTypeReqDescription
familystring–Optional family filter: target-15 (covered call), supercycle (thematic infrastructure) or shield (monthly buffer). Omit to list all 13 funds.
NameTypeReqDescription
disclosurestringyesDisclosure to show with the data.
fundsarrayyes–

No examples provided.

loss_recovery ~93

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/.

NameTypeReqDescription
loss_pctnumber–Loss, in percent (positive number, for example 30). Accepts 0 to 99; default 30.
NameTypeReqDescription
explanationstringyes–
gain_needed_to_recoverstringyes–
lossstringyes–
notestringyes–
pagestringyes–
value_of_100000_after_lossstringyes–

No examples provided.

search_faq ~122

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

NameTypeReqDescription
limitinteger–Maximum number of results to return. Accepts 1 to 10; default 5.
querystringyesQuestion or keywords, for example "When does OMAH pay distributions?". Required; words of three letters or fewer are ignored.
tickerstring–Optional: search only this fund's FAQs. Omit to search every fund page plus the family and About pages.
NameTypeReqDescription
disclosurestringyesDisclosure to show with the data.
resultsarrayyes–

No examples provided.

supercycle_spending ~115

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/.

NameTypeReqDescription
cyclestring–Which breakdown to return: ai, power, defense, space or robotics. Omit for all five.
NameTypeReqDescription
breakdownsarrayyes–
notestringyes–
pagestringyes–

No examples provided.

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.

remote · www.vistashares.com

# add to Claude Code
claude mcp add --transport http com-vistashares-etfs 'https://www.vistashares.com/mcp'
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.