Model Context Protocol low risk

Etf Flow

Delivers historical crypto ETF flow data, formatted as markdown tables, enabling AI agents to analyze investment trends for BTC and ETH.

Connections & Capabilities

Connects To

GitHubDiscord

Capabilities

read

Quickstart

Config

{
  "mcpServers": {
    "etf-flow-mcp": {
      "command": "uv",
      "args": ["--directory", "/absolute/path/to/etf-flow-mcp", "run", "etf-flow-mcp"],
      "env": { "COINGLASS_API_KEY": "your_coinglass_api_key_here" }
    }
  }
}

Exposed MCP Tools (1)

safe

get_etf_flow

Fetches historical ETF flow data for BTC or ETH and presents it in a markdown table.

Read-only operation; retrieves and formats existing data.

Safety Assessment

This MCP server is relatively safe due to its read-only nature and reliance on historical data. However, users should ensure secure handling of the CoinGlass API key and be aware of potential data inaccuracies from the external API. It is safe to use as long as the API key is secured and the data is validated.

Read-only access to ETF flow data.
No write or delete operations.
Data is historical, reducing real-time risk.
Requires API key for access, adding a layer of authentication.

Reliance on a third-party API (CoinGlass) introduces external dependency and potential data integrity issues.
Improper handling of the CoinGlass API key could lead to unauthorized access.
Data accuracy depends on the CoinGlass API; inaccuracies could mislead AI agents.
No built-in rate limiting, potentially leading to API overuse if not managed by the client.