_ registry / mcp streamable-http · checked 43m ago

vistashares

https://www.vistashares.com

Registry code: 18e84af2090eac6c

api record

Official read-only data from VistaShares (www.vistashares.com) on its 13 ETFs: Target 15® covered call ETFs, Supercycle® thematic infrastructure ETFs and Shield™ monthly buffer ETFs. Every figure carries the as-of date shown on the fund page; quote the date with the number and include the disclosure. No performance, rates or yields are provided; for those, link to the fund page. Calculator tools (covered_call_outcome, buffer_outcome, buffer_payoff_table, buffer_options_builder, buffer_mid_period, loss_recovery, etf_cost, supercycle_spending, ai_supply_chain_layers) run the same math as the…

endpoint
https://www.vistashares.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is vistashares live?
Yes — it answered the hub's last check (checked 43m ago). It answered 100% of checks over the last 30 days.
Is vistashares free to use?
Yes — the hub reached it with no key and no payment.
What tools does vistashares have?
15 tools: list_funds, search_faq, get_fund, get_holdings, get_distributions, get_documents, covered_call_outcome, buffer_outcome, ….
Is vistashares safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,484ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 15 tools
3 open 12 never probed 3 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • buffer_options_builder open 43m ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • ai_supply_chain_layers open 43m ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • buffer_mid_period open 43m ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "cap_pct": {
      "type": "number",
      "default": 12,
      "maximum": 200,
      "minimum": 0,
      "description": "Cap for the full period, in percent."
    },
    "buffer_pct": {
      "type": "number",
      "default": 10,
      "maximum": 100,
      "minimum": 0,
      "description": "Buffer size for the full period, in percent."
    },
    "fund_change_pct": {
      "type": "number",
      "default": 3,
      "maximum": 200,
      "minimum": -90,
      "description": "Fund value change since the period started, in percent."
    },
    "index_change_pct": {
      "type": "number",
      "default": 5,
      "maximum": 200,
      "minimum": -90,
      "description": "Index change since the period started, in percent."
    }
  }
}
    arguments 33 lines
  • list_funds unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "family": {
      "enum": [
        "target-15",
        "supercycle",
        "shield"
      ],
      "type": "string",
      "description": "target-15 (covered call), supercycle (thematic infrastructure) or shield (monthly buffer)."
    }
  }
}
    arguments 14 lines
  • search_faq unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Question or keywords."
    },
    "ticker": {
      "type": "string",
      "description": "Optional: limit to one fund."
    }
  }
}
    arguments 21 lines
  • get_fund unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "enum": [
        "OMAH",
        "ACKY",
        "DRKY",
        "TPRY",
        "SIOO",
        "QUSA",
        "AIS",
        "POW",
        "GALX",
        "RTOO",
        "AMMO",
        "VOOB",
        "QQQB"
      ],
      "type": "string",
      "description": "Fund ticker, for example OMAH, AIS or VOOB."
    }
  }
}
    arguments 27 lines
  • get_holdings unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "enum": [
        "OMAH",
        "ACKY",
        "DRKY",
        "TPRY",
        "SIOO",
        "QUSA",
        "AIS",
        "POW",
        "GALX",
        "RTOO",
        "AMMO",
        "VOOB",
        "QQQB"
      ],
      "type": "string",
      "description": "Fund ticker, for example OMAH, AIS or VOOB."
    }
  }
}
    arguments 27 lines
  • get_distributions unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "enum": [
        "OMAH",
        "ACKY",
        "DRKY",
        "TPRY",
        "SIOO",
        "QUSA",
        "AIS",
        "POW",
        "GALX",
        "RTOO",
        "AMMO",
        "VOOB",
        "QQQB"
      ],
      "type": "string",
      "description": "Fund ticker, for example OMAH, AIS or VOOB."
    }
  }
}
    arguments 27 lines
  • get_documents unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "enum": [
        "OMAH",
        "ACKY",
        "DRKY",
        "TPRY",
        "SIOO",
        "QUSA",
        "AIS",
        "POW",
        "GALX",
        "RTOO",
        "AMMO",
        "VOOB",
        "QQQB"
      ],
      "type": "string",
      "description": "Fund ticker, for example OMAH, AIS or VOOB."
    }
  }
}
    arguments 27 lines
  • covered_call_outcome unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "strike_pct": {
      "type": "number",
      "default": 5,
      "maximum": 100,
      "minimum": 0,
      "description": "Call strike, in percent above the current price."
    },
    "premium_pct": {
      "type": "number",
      "default": 2,
      "maximum": 50,
      "minimum": 0,
      "description": "Option premium received, in percent of the position."
    },
    "stock_return_pct": {
      "type": "number",
      "default": 8,
      "maximum": 200,
      "minimum": -100,
      "description": "Stock return over the option period, in percent (for example 8 or -12)."
    }
  }
}
    arguments 26 lines
  • buffer_outcome unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "cap_pct": {
      "type": "number",
      "default": 12,
      "maximum": 200,
      "minimum": 0,
      "description": "Cap on gains, in percent."
    },
    "buffer_pct": {
      "type": "number",
      "default": 10,
      "maximum": 100,
      "minimum": 0,
      "description": "Buffer size, in percent of losses absorbed first."
    },
    "index_return_pct": {
      "type": "number",
      "default": -15,
      "maximum": 200,
      "minimum": -100,
      "description": "Index return over the outcome period, in percent."
    }
  }
}
    arguments 26 lines
  • buffer_payoff_table unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "cap_pct": {
      "type": "number",
      "default": 12,
      "maximum": 200,
      "minimum": 0,
      "description": "Cap on gains, in percent."
    },
    "buffer_pct": {
      "type": "number",
      "default": 10,
      "maximum": 100,
      "minimum": 0,
      "description": "Buffer size, in percent."
    },
    "loss_share_beyond_buffer": {
      "type": "number",
      "default": 1,
      "maximum": 1,
      "minimum": 0,
      "description": "Share of losses beyond the buffer that the investor bears (1 = all, 0.5 = half)."
    }
  }
}
    arguments 26 lines
  • loss_recovery unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "loss_pct"
  ],
  "properties": {
    "loss_pct": {
      "type": "number",
      "default": 30,
      "maximum": 99,
      "minimum": 0,
      "description": "Loss, in percent (positive number, for example 30)."
    }
  }
}
    arguments 15 lines
  • etf_cost unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "years": {
      "type": "number",
      "default": 5,
      "maximum": 50,
      "minimum": 1,
      "description": "Holding period, in years."
    },
    "amount": {
      "type": "number",
      "default": 100000,
      "maximum": 1000000000,
      "minimum": 0,
      "description": "Amount invested, in dollars."
    },
    "spread_pct": {
      "type": "number",
      "default": 0.1,
      "maximum": 5,
      "minimum": 0,
      "description": "Round-trip bid-ask spread, in percent."
    },
    "expense_ratio_pct": {
      "type": "number",
      "default": 0.5,
      "maximum": 5,
      "minimum": 0,
      "description": "Expense ratio, in percent per year."
    }
  }
}
    arguments 33 lines
  • supercycle_spending unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "cycle": {
      "enum": [
        "ai",
        "power",
        "defense",
        "space",
        "robotics"
      ],
      "type": "string",
      "description": "Which breakdown to return. Omit for all five."
    }
  }
}
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 18e84af2090eac6c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/18e84af2090eac6c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/18e84af2090eac6c/badge.svg)](https://brick.blue/agent/18e84af2090eac6c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.