Skip to main content
Glama
free-etf-flows-mcp

free-etf-flows-mcp

by yasinozen35

ETF Flows MCP Server — Spot Bitcoin & Ethereum ETF Flows for AI Assistants

Website Remote MCP OpenAPI License

Give Claude, ChatGPT, Cursor, VS Code or any MCP client daily net flows for every US spot Bitcoin and Ethereum ETF — IBIT, FBTC, GBTC, ARKB, ETHA, FETH, ETHE and more.


Claude → Settings → Connectors → Add custom connector → https://yasinozen.com/etf-flows/mcp

Claude Code

claude mcp add --transport http etf-flows https://yasinozen.com/etf-flows/mcp

Cursor / Windsurf / VS Code (mcp.json)

{
  "mcpServers": {
    "etf-flows": {
      "url": "https://yasinozen.com/etf-flows/mcp",
      "headers": { "X-API-Key": "YOUR_KEY" }
    }
  }
}

The key is optional. Clients that cannot send headers can use https://yasinozen.com/etf-flows/mcp?api_key=YOUR_KEY. One-click install links for Cursor and VS Code are on the setup page.

Related MCP server: etf-flow-mcp

Tools

Tool

Description

get_etf_flow_summary

Latest day, 7/30-day, month-to-date, YTD and cumulative flows, streaks and top funds (remote server)

get_latest_etf_flows

Daily totals for the most recent trading days, optional per-fund breakdown

get_etf_flows_by_date_range / query_etf_flows_by_date_range

Daily totals between two dates

get_fund_flows

Daily flows and cumulative total for one ETF (e.g. IBIT)

get_pro_access_info

Plans and how to get a key

Example prompts: “Summarize spot Bitcoin ETF flows this week”, “Did IBIT have outflows in the last 10 days?”, “Compare Ethereum ETF flows in August and September.”

Run locally (stdio)

Requires uv.

{
  "mcpServers": {
    "etf-flows": {
      "command": "uv",
      "args": ["--directory", "/absolute/path/to/free-etf-flows-mcp", "run", "python", "mcp_server.py"],
      "env": { "ETF_FLOWS_API_KEY": "YOUR_KEY" }
    }
  }
}

Plans

Preview (no key)

Free key

Pro ($9.99/mo)

History

7 trading days

90 trading days

Full, since Jan 2024

Delay

1 day

1 day

Same day

Per-fund data

–

✓

✓

CSV export

–

–

✓

Rate limit

10/min

30/min

120/min

👉 Get a free key · Upgrade to Pro

Data

Daily figures are sourced from the public ETF flow tables of Farside Investors and normalized to US dollars (parenthesized values become negative). See the methodology. This project is independent and not affiliated with Farside Investors or any ETF issuer. Not investment advice.


Built by Yasin Özen ·

Available Tools

3 tools
get_latest_etf_flowsAInspect

Fetch the most recent Spot ETF flow records for a given ticker (BTC or ETH).

Args: ticker: The asset ticker, either 'BTC' or 'ETH' (default 'BTC')

Inputs: ticker. Returns: result

get_pro_access_infoAInspect

Get information on how to upgrade to a Pro API Key for unlimited real-time Spot ETF flow queries.

Inputs: no named parameters. Returns: result

query_etf_flows_by_date_rangeAInspect

Query historical ETF flows within a specific date range.

Args: start_date: Start date in YYYY-MM-DD format end_date: End date in YYYY-MM-DD format ticker: Optional asset ticker ('BTC' or 'ETH') to filter the query

Inputs: end_date (required), start_date (required), ticker. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: one fetches latest flows, one queries a date range, and one provides account upgrade info. No overlap or ambiguity in their roles.

    Naming Consistency4/5

    All names follow a verb-noun pattern, but 'query' in the second tool is a slight deviation from the 'get' used in the other two. Overall, names are clear and predictable.

    Tool Count4/5

    Three tools is a reasonable count for a focused ETF flow server, though it sits at the lower boundary of the typical well-scoped range. The purpose is narrow, so the count feels appropriate.

    Completeness4/5

    The tools cover the core data retrieval needs: latest flows and historical range queries. A minor gap is the lack of a direct 'get all flows' without a date range, but users can work around with broad dates. The pro access tool adds useful context.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers