Skip to content

cryptoetf MCP server

io.github.sly13/cryptoetfsly13streamable-httpv1.0.14Scanned

Live spot crypto ETF flows for 16 assets and their funds, CEFI index and prices.

12 tools: 12 only read.

Tools: 0 delete, 0 irreversible, 0 write, 12 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the cryptoetf MCP server can do

The cryptoetf MCP server is published by the GitHub account sly13. It has 12 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 1.0.14.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Only reads 12Show 12 read-only tools
  • get_asset_flowsGet daily net ETF flow history for a single crypto asset over the last 30 days.No findings

    Why it is in this group

    • The name "get_asset_flows" says "get": a word for reading.
    Description, as the server wrote it
    Get daily net ETF flow history for a single crypto asset over the last 30 days. Returns a time series of net USD millions per day (positive = inflow, negative = outflow). Figures are asset-level totals; the per-fund breakdown (IBIT, FBTC, ETHA and others) is returned by get_fund_flows.

    Annotations the server declares

    • title: Crypto ETF Flow History
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_btc_etf_vs_minersGet net creations of US spot Bitcoin ETFs in BTC against newly mined bitcoin.No findings

    Why it is in this group

    • The name "get_btc_etf_vs_miners" says "get": a word for reading.
    Description, as the server wrote it
    Get net creations of US spot Bitcoin ETFs in BTC against newly mined bitcoin. Windows: the last full week (Monday to Sunday), 30 days, year to date and since launch (11 Jan 2024), each with ETF net BTC, mined BTC and their ratio (null when ETFs had net outflows). Also the number of consecutive full weeks with ETF demand above new supply and the last 12 weeks. ETF BTC is the daily USD net flow divided by the volume-weighted bitcoin price of that day; mined BTC is the block subsidy times blocks between midnights UTC.

    Annotations the server declares

    • title: Bitcoin ETFs vs Miners
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_cefi_indexReturns the composite CEFI (Crypto ETF Flow Index): a 0–100 index of money moving through US spot crypto ETFs on all 16 tracked assets.No findings

    Why it is in this group

    • The name "get_cefi_index" says "get": a word for reading.
    Description, as the server wrote it
    Returns the composite CEFI (Crypto ETF Flow Index): a 0–100 index of money moving through US spot crypto ETFs on all 16 tracked assets. Net flows of all funds are added up in dollars, and three components are scored against the past year: flow (today's net flow, smoothed, 40%), trend (net flow over 20 trading days, 30%) and breadth (share of funds with inflows, 30%). 50 = zero net flow; a typical inflow day scores about 69, a typical outflow day about 31. Each component is on the same 0–100 scale. Zones: 0–20 extreme fear, 20–40 fear, 40–60 neutral, 60–80 greed, 80–100 extreme greed.

    Annotations the server declares

    • title: CEFI Sentiment Index
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_cost_basisGet the estimated average entry price per coin of US spot crypto ETF holders for one asset or all 16: coins accumulated through net flows, money invested, average entry, the latest…No findings

    Why it is in this group

    • The name "get_cost_basis" says "get": a word for reading.
    Description, as the server wrote it
    Get the estimated average entry price per coin of US spot crypto ETF holders for one asset or all 16: coins accumulated through net flows, money invested, average entry, the latest coin price and unrealised P&L. Also how many consecutive days holders have been above or below their entry and since when. The entry is built from daily creations and redemptions valued at the volume-weighted price of each day; coins of converted trusts (GBTC, ETHE) are not included.

    Annotations the server declares

    • title: ETF Holders Average Entry Price
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_etf_holdingsGet the coins held in trust by US spot crypto ETFs for one asset or all 16, and the share of the coin's circulating supply they represent (`supplyPct`, percent).No findings

    Why it is in this group

    • The name "get_etf_holdings" says "get": a word for reading.
    Description, as the server wrote it
    Get the coins held in trust by US spot crypto ETFs for one asset or all 16, and the share of the coin's circulating supply they represent (`supplyPct`, percent). Per fund: coins held, share of the asset's ETF coins and `coinsBasis` — reported (published by the issuer, or shares times the published coins per share) or estimated (net assets per share at the same-day coin price, for issuers that do not publish coins). Includes 7- and 30-day changes in coins and the last 30 days of daily history.

    Annotations the server declares

    • title: Crypto Held by ETFs
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_flows_summaryGet the latest-day net ETF inflow/outflow (USD millions) for every tracked crypto asset: BTC (Bitcoin), ETH (Ethereum), SOL (Solana), XRP, HYP (Hyperliquid), DOGE (Dogecoin), LINK …No findings

    Why it is in this group

    • The name "get_flows_summary" says "get": a word for reading.
    Description, as the server wrote it
    Get the latest-day net ETF inflow/outflow (USD millions) for every tracked crypto asset: BTC (Bitcoin), ETH (Ethereum), SOL (Solana), XRP, HYP (Hyperliquid), DOGE (Dogecoin), LINK (Chainlink), AVAX (Avalanche), HBAR (Hedera), LTC (Litecoin), BNB, DOT (Polkadot), SUI, NEAR, TRX (TRON) and ZEC (Zcash). Positive = inflow, negative = outflow. Flows are published one business day in arrears, so `referenceIsToday` is normally false: the figures belong to `referenceDate`, the last trading day published, not to the current date. On Mondays the freshest data is Friday's. `totalUsdM` is the sum across all assets for `referenceDate`. `netFlowUsdM` is null for an asset that has no figure for `referenceDate` yet; its latest reported day is then in `lastReportedDate`, and it is not part of `totalUsdM`. Figures are asset-level totals; the per-fund breakdown (IBIT, FBTC, ETHA and others) is returned by get_fund_flows, net assets by get_funds.

    Annotations the server declares

    • title: Latest Crypto ETF Flows
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_fund_flowsGet daily net flows of every spot ETF on one crypto asset, fund by fund (IBIT, FBTC, ETHA, …), over the last 30 days.No findings

    Why it is in this group

    • The name "get_fund_flows" says "get": a word for reading.
    Description, as the server wrote it
    Get daily net flows of every spot ETF on one crypto asset, fund by fund (IBIT, FBTC, ETHA, …), over the last 30 days. Each trading day lists the funds trading that day with ticker, issuer and net USD millions (positive = inflow, negative = outflow), plus `totalUsdM` for the day. `netFlowUsdM` is null when there is no figure for the fund that day, usually because it has not reported yet; 0 means no creations or redemptions. Flows are published one business day in arrears.

    Annotations the server declares

    • title: Crypto ETF Flows by Fund
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_fundsGet the US spot crypto ETFs that have started trading, for one asset or all 16: ticker, name, issuer, exchange, listing date, sponsor fee (percent per year), current net assets (`n…No findings

    Why it is in this group

    • The name "get_funds" says "get": a word for reading.
    Description, as the server wrote it
    Get the US spot crypto ETFs that have started trading, for one asset or all 16: ticker, name, issuer, exchange, listing date, sponsor fee (percent per year), current net assets (`netAssetsUsdM`, USD millions) and coins held, plus the total net assets of each asset. Net assets are a current snapshot, not a history. `netAssetsBasis` is reported (published by the issuer for `netAssetsDate`), repriced (the latest published figure moved to that day by the NAV change of other funds) or estimated (coins times price, for issuers without daily holdings). `coinsHeld` is null for issuers that do not publish holdings in coins. Each fund also has `effectiveFeePct` and `feeWaiver` (a fee waiver in effect today), `feeRevenueUsdMPerYear` (net assets times the fee charged today, USD millions), `supplySharePct` (its coins as a share of circulating supply), `staking` (status from SEC filings, share staked, net yield and how rewards are paid) and `delistedAt` for a closed fund.

    Annotations the server declares

    • title: Crypto ETF Fund Directory
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_issuer_revenueGet estimated sponsor fee revenue of US spot crypto ETFs: net assets times the prospectus sponsor fee, with temporary fee waivers applied.No findings

    Why it is in this group

    • The name "get_issuer_revenue" says "get": a word for reading.
    Description, as the server wrote it
    Get estimated sponsor fee revenue of US spot crypto ETFs: net assets times the prospectus sponsor fee, with temporary fee waivers applied. Per fund: net assets, nominal and effective fee (percent per year), revenue per day and annualised at current assets, and the sum for the last 30 days where a daily series exists. Totals by issuer and for the whole market. Arithmetic on the published fee, not the issuer's reported revenue; the sponsor's share of staking rewards is not included.

    Annotations the server declares

    • title: Crypto ETF Issuer Fee Revenue
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_pricesGet current spot prices (USD) and 24-hour percentage change for all 16 tracked crypto assets: BTC, ETH, SOL, XRP, HYP, DOGE, LINK, AVAX, HBAR, LTC, BNB, DOT, SUI, NEAR, TRX, ZEC.No findings

    Why it is in this group

    • The name "get_prices" says "get": a word for reading.
    Description, as the server wrote it
    Get current spot prices (USD) and 24-hour percentage change for all 16 tracked crypto assets: BTC, ETH, SOL, XRP, HYP, DOGE, LINK, AVAX, HBAR, LTC, BNB, DOT, SUI, NEAR, TRX, ZEC. Prices are sourced from major exchanges and refreshed frequently.

    Annotations the server declares

    • title: Crypto Spot Prices
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_stakingGet the staking status of US spot crypto ETFs: active, allowed_not_started, pending_amendment, no, not_stakeable (proof-of-work assets and XRP) or unknown, from SEC filings.No findings

    Why it is in this group

    • The name "get_staking" says "get": a word for reading.
    Description, as the server wrote it
    Get the staking status of US spot crypto ETFs: active, allowed_not_started, pending_amendment, no, not_stakeable (proof-of-work assets and XRP) or unknown, from SEC filings. For staking funds: cap and share of assets staked, the staking yield as disclosed by the issuer with its date, providers, whether rewards are kept in the fund or paid in cash, the last cash payout per share, and `coinsPerShare` — the annualised growth of coins behind each share from daily issuer snapshots (shown only where the series is clean). Per asset: funds staking and the estimated coins staked.

    Annotations the server declares

    • title: Staking Inside Crypto ETFs
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • get_weekly_analyticsGet 7-day aggregated ETF flow analytics for all tracked assets.No findings

    Why it is in this group

    • The name "get_weekly_analytics" says "get": a word for reading.
    Description, as the server wrote it
    Get 7-day aggregated ETF flow analytics for all tracked assets. Returns total net flow, the number of trading days in the window, average flow per trading day, and count of positive vs negative days per asset. Weekends are excluded. A compact momentum summary without the full daily series.

    Annotations the server declares

    • title: Weekly ETF Flow Analytics
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:11 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools12 changed.~12 changedView diff
  2. Tools5 added, 2 changed.+5 added~2 changedView diff

Install

Pinned to version 1.0.14. Values in angle brackets are yours to fill in.

claude mcp add --transport http cryptoetf https://mcp.cryptoetf.today/mcp
claude mcp add --transport http cryptoetf https://mcp.cryptoetf.today/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__cryptoetf__get_flows_summary",
      "mcp__cryptoetf__get_asset_flows",
      "mcp__cryptoetf__get_fund_flows",
      "mcp__cryptoetf__get_funds",
      "mcp__cryptoetf__get_cefi_index",
      "mcp__cryptoetf__get_prices",
      "mcp__cryptoetf__get_weekly_analytics",
      "mcp__cryptoetf__get_etf_holdings",
      "mcp__cryptoetf__get_btc_etf_vs_miners",
      "mcp__cryptoetf__get_issuer_revenue",
      "mcp__cryptoetf__get_staking",
      "mcp__cryptoetf__get_cost_basis"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cryptoetf. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.sly13/cryptoetf/verify?hash=444063e0c416f6bdbe38f434ee5d11d2354b95d6ee6ffef9171e3a07c45afb82" | jq -e '.changed == false'

Pinned hash 444063e0c416, from Nov 19, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.sly13/cryptoetf/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.sly13/cryptoetf
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.sly13/cryptoetf.svg)](https://radar.anlyon.com/servers/io.github.sly13/cryptoetf)

Source: MCP Registry · repository. Synced Nov 19, 2026, 01:18 UTC.

cryptoetf MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the cryptoetf MCP server safe?

No scan can promise that. What its definitions show: 12 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the cryptoetf MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the cryptoetf MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the cryptoetf MCP server have?

12 tools: 12 read. get_flows_summary, get_asset_flows, get_fund_flows, get_funds, get_cefi_index, get_prices, get_weekly_analytics, get_etf_holdings and 4 more.

Does the cryptoetf MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the cryptoetf MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the cryptoetf MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.