CryptoETF MCP — spot crypto ETF flows for AI agents
[npm]
[npm downloads]
[MCP Registry]
The Model Context Protocol surface of
cryptoetf.today: daily net flows for every US-listed
spot crypto ETF complex and every fund in it, fund AUM, the CEFI sentiment index and live coin prices — for
Claude, Cursor, Codex, Gemini CLI and any other MCP-capable agent.
Sixteen assets: BTC, ETH, SOL, XRP, HYPE, DOGE, LINK, AVAX, HBAR, LTC, BNB,
DOT, SUI, NEAR, TRX, ZEC. Flow figures are net USD millions, sourced from the issuers' own
daily reports; for the eleven smaller complexes there is no market-wide
aggregator, so the numbers are computed from each issuer's fund pages.
You probably don't need to install anything. The server is hosted, and every
client that speaks remote MCP can reach it directly:
No API key, no account — the endpoint is open.
Setup per client
Claude Code — one command, no restart:
Cursor — .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
Claude Desktop and other stdio-only clients — this package is the bridge.
claude_desktop_config.json, then restart the app fully:
Nothing to install by hand: npx fetches the package on first run. It has zero
dependencies and simply forwards JSON-RPC between stdin/stdout and the hosted
endpoint.
Tools
History reaches back 30 days, in the tools and in the
REST API alike. Longer history is on
cryptoetf.today.
Ask it things like
- "What are today's crypto ETF flows?"
- "Compare BTC and ETH ETF flows over the past month"
- "Which asset had the strongest week of inflows?"
- "Is the CEFI index bullish right now?"
Configuration
Requires Node.js 18 or newer.
Data and limits
Flow data is updated every business day as issuers publish. Figures are
informational — this is market data, not investment advice.
Privacy Policy
Full policy: cryptoetf.today/en/privacy.
What is collected. The bridge forwards your JSON-RPC requests to
https://mcp.cryptoetf.today/api/mcp and returns the responses. The only
request data that leaves your machine is the tool name and its arguments (an
asset ticker, at most). Conversation content, files and credentials are never
read or transmitted.
How it is used and stored. The server logs the standard request metadata of
any web service — IP address, timestamp, endpoint — and keeps a per-IP counter
in Redis to enforce the 60 requests/minute rate limit. Logs are retained for 30
days and are used only to operate and protect the service.
Third-party sharing. None. Request data is not sold, shared or passed to any
third party. The service is operated by us and calls only our own API.
Retention. Rate-limit counters expire within a minute; request logs within
30 days. No user accounts and no personal profiles exist — the endpoint is open
and unauthenticated.
Contact. github.com/zerosix-studio/cryptoetf-mcp/issues
or the contact form at cryptoetf.today.
Releasing
Bump the version in package.json, then tag the commit:
The Publish to npm workflow runs the bridge against the live server, skips
the publish if that version is already in the registry, and otherwise pushes it
with provenance — the npm page then links back to the exact workflow run and
commit the tarball was built from.
MIT licensed.