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.

io.github.sly13/cryptoetf

REMOTE · MCP.CRYPTOETF.TODAY · 2 COMPONENTS

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

71 Trust /100

Last scanned (18 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

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 Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2091 tokens (~174/item across 12 items; 12 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 Management7
  • Stability observed for 2 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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
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.

  • 21 Nov 26 +1

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

  • 20 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 19 Nov 26 70

    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://mcp.cryptoetf.today/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cryptoetf.today CN=WE1,O=Google Trust Services,C=US 18 Nov 2026 16 Feb 2027 ECDSA 256 ECDSA-SHA256 7cdc5ba9bb8a74240e867fa3726ab5f9
SANs: cryptoetf.today, *.cryptoetf.today
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.cryptoetf.today. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
today. DS published 8092 8 Verified
cryptoetf.today. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.cryptoetf.today/mcp Verified 200
http (plaintext) http://mcp.cryptoetf.today/mcp HTTPS enforced 301 https://mcp.cryptoetf.today/mcp
MCP tools · 12 exposed · ~2,009 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
get_asset_flows ~130

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.

NameTypeReqDescription
assetstringyesAsset to fetch: btc, eth, sol, xrp, hyp, doge, link, avax, hbar, ltc, bnb, dot, sui, near, trx, zec

No output schema declared.

No examples provided.

get_btc_etf_vs_miners ~131

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_cefi_index ~174

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_cost_basis ~157

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.

NameTypeReqDescription
assetstring–Optional asset filter: btc, eth, sol, xrp, hyp, doge, link, avax, hbar, ltc, bnb, dot, sui, near, trx, zec

No output schema declared.

No examples provided.

get_etf_holdings ~176

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.

NameTypeReqDescription
assetstring–Optional asset filter: btc, eth, sol, xrp, hyp, doge, link, avax, hbar, ltc, bnb, dot, sui, near, trx, zec

No output schema declared.

No examples provided.

get_flows_summary ~269

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_fund_flows ~181

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.

NameTypeReqDescription
assetstringyesAsset to fetch: btc, eth, sol, xrp, hyp, doge, link, avax, hbar, ltc, bnb, dot, sui, near, trx, zec

No output schema declared.

No examples provided.

get_funds ~291

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.

NameTypeReqDescription
assetstring–Optional asset filter: btc, eth, sol, xrp, hyp, doge, link, avax, hbar, ltc, bnb, dot, sui, near, trx, zec

No output schema declared.

No examples provided.

get_issuer_revenue ~165

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.

NameTypeReqDescription
assetstring–Optional asset filter for the fund list: btc, eth, sol, xrp, hyp, doge, link, avax, hbar, ltc, bnb, dot, sui, near, trx, zec

No output schema declared.

No examples provided.

get_prices ~80

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_staking ~186

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.

NameTypeReqDescription
assetstring–Optional asset filter: btc, eth, sol, xrp, hyp, doge, link, avax, hbar, ltc, bnb, dot, sui, near, trx, zec

No output schema declared.

No examples provided.

get_weekly_analytics ~69

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.sly13/cryptoetf MCP server?

io.github.sly13/cryptoetf is a hosted endpoint at https://mcp.cryptoetf.today/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 · mcp.cryptoetf.today

# add to Claude Code
claude mcp add --transport http sly13-cryptoetf 'https://mcp.cryptoetf.today/mcp'
Common questions

What is the io.github.sly13/cryptoetf MCP server?

io.github.sly13/cryptoetf is an MCP server listed in the public MCP registry as io.github.sly13/cryptoetf. Live spot crypto ETF flows for 16 assets and their funds, CEFI index and prices. This page covers its hosted endpoint (https://mcp.cryptoetf.today/mcp).

Is the io.github.sly13/cryptoetf MCP server safe to use?

io.github.sly13/cryptoetf scores 71 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 io.github.sly13/cryptoetf MCP server expose?

io.github.sly13/cryptoetf exposes 12 tools: get_flows_summary, get_asset_flows, get_fund_flows, get_funds, get_cefi_index, and 7 more. Their descriptions and schemas cost roughly 2,009 tokens of context every time the server is loaded.

Does the io.github.sly13/cryptoetf MCP server require authentication?

No. We connected to io.github.sly13/cryptoetf without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.sly13/cryptoetf MCP server still maintained?

io.github.sly13/cryptoetf 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 io.github.sly13/cryptoetf MCP server?

VerifyMCP ran 13 checks on io.github.sly13/cryptoetf, 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.