{
  "markdown": "# CryptoETF MCP — spot crypto ETF flows for AI agents\n\n[![npm](https://img.shields.io/npm/v/@zerosix-studio/cryptoetf-mcp?color=cb3837&logo=npm)](https://www.npmjs.com/package/@zerosix-studio/cryptoetf-mcp)\n[![npm downloads](https://img.shields.io/npm/dm/@zerosix-studio/cryptoetf-mcp?color=cb3837)](https://www.npmjs.com/package/@zerosix-studio/cryptoetf-mcp)\n[![MCP Registry](https://img.shields.io/badge/MCP%20Registry-io.github.sly13%2Fcryptoetf-5b6cff)](https://registry.modelcontextprotocol.io)\n\nThe [Model Context Protocol](https://modelcontextprotocol.io) surface of\n[cryptoetf.today](https://cryptoetf.today): daily net flows for every US-listed\nspot crypto ETF complex, the CEFI sentiment index and live coin prices — for\nClaude, Cursor, Codex, Gemini CLI and any other MCP-capable agent.\n\nThirteen assets: **BTC, ETH, SOL, XRP, HYPE, DOGE, LINK, AVAX, HBAR, LTC, BNB,\nDOT, SUI**. Flow figures are net USD millions, sourced from the issuers' own\ndaily reports; for the eight smaller complexes there is no market-wide\naggregator, so the numbers are computed from each issuer's fund pages.\n\n**You probably don't need to install anything.** The server is hosted, and every\nclient that speaks remote MCP can reach it directly:\n\n```\nhttps://mcp.cryptoetf.today/api/mcp     Streamable HTTP · JSON-RPC 2.0\n```\n\nNo API key, no account — the endpoint is open.\n\n## Setup per client\n\n**Claude Code** — one command, no restart:\n\n```bash\nclaude mcp add --transport http cryptoetf https://mcp.cryptoetf.today/api/mcp\n```\n\n**Cursor** — `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global):\n\n```json\n{\n  \"mcpServers\": {\n    \"cryptoetf\": { \"url\": \"https://mcp.cryptoetf.today/api/mcp\" }\n  }\n}\n```\n\n**Claude Desktop and other stdio-only clients** — this package is the bridge.\n`claude_desktop_config.json`, then restart the app fully:\n\n```json\n{\n  \"mcpServers\": {\n    \"cryptoetf\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@zerosix-studio/cryptoetf-mcp\"]\n    }\n  }\n}\n```\n\nNothing to install by hand: `npx` fetches the package on first run. It has zero\ndependencies and simply forwards JSON-RPC between stdin/stdout and the hosted\nendpoint.\n\n## Tools\n\n| Tool | What it returns |\n|---|---|\n| `get_flows_summary` | Latest-day net flow for all 13 assets, with the date each figure belongs to |\n| `get_asset_flows` | Daily net flow history for one asset over the last 30 days |\n| `get_weekly_analytics` | 7-day totals per asset: net flow, average day, positive/negative day counts |\n| `get_cefi_index` | Composite CEFI sentiment score (baseline 100; above = bullish) |\n| `get_prices` | Spot price and 24h change for every tracked asset |\n\nHistory reaches back 30 days. Deeper history and per-fund breakdowns live in the\n[REST API](https://cryptoetf.today/en/api).\n\n## Ask it things like\n\n- \"What are today's crypto ETF flows?\"\n- \"Compare BTC and ETH ETF flows over the past month\"\n- \"Which asset had the strongest week of inflows?\"\n- \"Is the CEFI index bullish right now?\"\n\n## Configuration\n\n| Variable | Default | Purpose |\n|---|---|---|\n| `CRYPTOETF_MCP_URL` | `https://mcp.cryptoetf.today/api/mcp` | Point the bridge at another endpoint |\n| `CRYPTOETF_API_KEY` | — | Sent as `Authorization: Bearer …` when set; the public endpoint does not need it |\n\nRequires Node.js 18 or newer.\n\n## Data and limits\n\nFlow data is updated every business day as issuers publish. Figures are\ninformational — this is market data, not investment advice.\n\n- Website: [cryptoetf.today](https://cryptoetf.today)\n- REST API and MCP docs: [cryptoetf.today/en/api](https://cryptoetf.today/en/api)\n\n## Privacy Policy\n\nFull policy: [cryptoetf.today/en/privacy](https://cryptoetf.today/en/privacy).\n\n**What is collected.** The bridge forwards your JSON-RPC requests to\n`https://mcp.cryptoetf.today/api/mcp` and returns the responses. The only\nrequest data that leaves your machine is the tool name and its arguments (an\nasset ticker, at most). Conversation content, files and credentials are never\nread or transmitted.\n\n**How it is used and stored.** The server logs the standard request metadata of\nany web service — IP address, timestamp, endpoint — and keeps a per-IP counter\nin Redis to enforce the 60 requests/minute rate limit. Logs are retained for 30\ndays and are used only to operate and protect the service.\n\n**Third-party sharing.** None. Request data is not sold, shared or passed to any\nthird party. The service is operated by us and calls only our own API.\n\n**Retention.** Rate-limit counters expire within a minute; request logs within\n30 days. No user accounts and no personal profiles exist — the endpoint is open\nand unauthenticated.\n\n**Contact.** [github.com/zerosix-studio/cryptoetf-mcp/issues](https://github.com/zerosix-studio/cryptoetf-mcp/issues)\nor the contact form at [cryptoetf.today](https://cryptoetf.today).\n\n## Releasing\n\nBump the version in `package.json`, then tag the commit:\n\n```bash\ngit tag v1.0.4 && git push --tags\n```\n\nThe `Publish to npm` workflow runs the bridge against the live server, skips\nthe publish if that version is already in the registry, and otherwise pushes it\nwith provenance — the npm page then links back to the exact workflow run and\ncommit the tarball was built from.\n\nMIT licensed.\n",
  "bytes": 5218,
  "sha": "dc77502cdc765de98f0fbcabfb78f825407fedfedd23daf3b2102d0700fb550a",
  "repo_slug": "zerosix-studio/cryptoetf-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_sly13_cryptoetf_989ede2d/readme"
}