Finance · Remote MCP server
US Spot Bitcoin & Ethereum ETF Flows
Daily net flows for US spot Bitcoin & Ethereum ETFs (IBIT, FBTC, GBTC, ETHA) with per-fund history.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.yasinozen/etf-flows- Version
- 1.1.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-09-13
- Updated
- 2026-09-13
- Publisher
- com.yasinozen
- Namespace
- Namespace verified by the MCP Registry via the domain yasinozen.com · how
- Listed under
- Bitcoin MCP servers, Ethereum MCP servers
- Website
- yasinozen.com/etf-flows/mcp-server/
- Repository
- github.com/yasinozen35/free-etf-flows-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://yasinozen.com/etf-flows/mcp | X-API-Key (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 410)
- Handshake
- HTTP 410
- Checked on
- 2026-10-05
How to connect US Spot Bitcoin & Ethereum ETF Flows
US Spot Bitcoin & Ethereum ETF Flows is a remote MCP server: there is nothing to install. Its endpoint is https://yasinozen.com/etf-flows/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: X-API-Key (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| Uruguay Invoices (DGI e-Factura CFE, merchant-signed SOAP relay)Uruguay DGI e-Factura (CFE): AI agents submit signed sobres to DGI e-invoicing, stateless forwarder. | Remote · HTTPLive check: ✗ no handshake |
| US Company Intelligence for AI Agents (SEC EDGAR, x402)SEC EDGAR company briefs for agents: cited synthesis, XBRL metrics. x402/USDC, no account. | Remote · HTTPLive check: ✓ handshake |
| Us Congress TradesUS Congress stock trades and financial disclosures by member, ticker, or date, hosted MCP. | Remote · HTTPLive check: sign-in required |
| US Economic, SEC EDGAR & On-Chain Data (x402)21 paid tools: US macro data, SEC EDGAR filings, on-chain EVM reads. Settled in USDC on Base. | Remote · HTTPLive check: ✓ handshake |
| US Stocks & Market DataUS market snapshot, stock fundamentals, prices, statements, news and analyst views. | Remote · HTTPLive check: ✓ handshake |
| Us Tariff LedgerUS tariff & trade truth: duty actually paid by origin/HS 2017+, HTS rulebook, CBP rulings. No key. | Remote · HTTPLive check: ✓ handshake |
| Usdi MCP ServerLive tools for USDi: CPI-indexed exchange rate, contract/pool addresses, and mint/redeem mechanics. | Remote · HTTPLive check: ✓ handshake |
| User Agent Parser APIParse user agents — browser, OS, device, bot detection. x402 micropayment. | Remote · SSELive check: ✗ no handshake |