en es ja ko zh

etf-flow-mcp

Name: etf-flow-mcp
Author: kukapay

by kukapay

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Flujo de ETF MCP

Un servidor MCP que entrega datos de flujo de ETF criptográficos para impulsar la toma de decisiones de los agentes de IA.

Discordia Pitón Licencia Estado

Características

Herramienta unificada : la herramienta get_etf_flow obtiene dinámicamente datos históricos de flujo de ETF para BTC o ETH.
Salida de tabla de Markdown : aprovecha las tablas dinámicas para presentar datos con tickers de ETF como columnas, fechas como filas y una columna de totales para flujos sumados.
Orientación rápida : incluye una guía ( etf_flow_prompt ) para agilizar las interacciones de LLM para realizar consultas fáciles de usar.

Related MCP server: crypto-portfolio-mcp

Prerrequisitos

Python : versión 3.10 o superior.
uv : Un administrador de proyectos y paquetes de Python rápido ( instrucciones de instalación ).
Clave API de CoinGlass : obtenga una clave de CoinGlass .
Claude Desktop : Opcional, para consultas interactivas.
Git : para clonar el repositorio.

Instalación

Clonar el repositorio :

git clone https://github.com/kukapay/etf-flow-mcp.git
cd etf-flow-mcp

Configurar con uv : Instalar dependencias usando uv :
```
uv sync
```

Uso

Integración con Claude Desktop

Configurar Claude Desktop : agregue el servidor a claude_desktop_config.json (ubicado en ~/Library/Application Support/Claude en macOS o %APPDATA%\Claude en Windows):
```
{
  "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" }
    }
  }
}
```
Reemplace /absolute/path/to/etf-flow-mcp/cli.py con la ruta completa a cli.py .
Reiniciar Claude Desktop : Verifique que el ícono del martillo aparezca en la interfaz de usuario de Claude Desktop para confirmar que el servidor esté cargado.
Ejemplos de consultas :
- "Muéstrame los últimos datos de flujo del ETF de BTC en una tabla"
- Obtener el historial de flujo del ETF de ETH

Ejemplo de salida

Flujo de ETF de BTC :

| Date       | GBTC      | IBIT      | FBTC      | ARKB      | BITB      | BTCO     | HODL     | BRRR     | EZBC     | BTCW     | Total     |
|------------|-----------|-----------|-----------|-----------|-----------|----------|----------|----------|----------|----------|-----------|
| 2025-04-24 | 0         | 327300000 | 0         | 97700000  | 10200000  | 7750000  | 0        | 0        | 0        | 0        | 442200000 |
| 2025-04-23 | 0         | 643200000 | 124400000 | 129500000 | -15200000 | 0        | 5300000  | 0        | 0        | 0        | 917700000 |
| 2025-04-22 | 65100000  | 193500000 | 253800000 | 267100000 | 76700000  | 18300000 | 6500000  | 0        | 10600000 | 0        | 912700000 |
| 2025-04-21 | 36600000  | 41600000  | 88100000  | 116100000 | 45100000  | 0        | 11700000 | 0        | 10100000 | 0        | 381300000 |
| 2025-04-18 | 0         | 0         | 0         | 0         | 0         | 0        | 0        | 0        | 0        | 0        | 0         |

Flujo de ETF de ETH :

| Date       | ETHE      | GETH     | ETHA      | ETHW     | FETH      | ETHV     | EZET     | CETH     | QETH     | Total     |
|------------|-----------|----------|-----------|----------|-----------|----------|----------|----------|----------|-----------|
| 2025-04-24 | -6600000  | 18300000 | 40000000  | 5100000  | 0         | 2600000  | 0        | 4100000  | 0        | 63550000  |
| 2025-04-23 | 0         | 6400000  | -30300000 | 0        | 0         | 0        | 0        | 0        | 0        | -23900000  |
| 2025-04-22 | 0         | 0        | 0         | 6100000  | 32700000  | 0        | 0        | 0        | 0        | 38800000  |
| 2025-04-21 | -25400000 | 0        | 0         | 0        | 0         | 0        | 0        | 0        | 0        | -25400000  |
| 2025-04-18 | 0         | 0        | 0         | 0        | 0         | 0        | 0        | 0        | 0        | 0         |
| 2025-04-17 | 0         | 0        | 0         | 0        | 0         | 0        | 0        | 0        | 0        | 0         |

Licencia

Este proyecto está licenciado bajo la licencia MIT .

Available Tools

1 tool

get_etf_flowA

Fetch historical ETF flow data for BTC or ETH from CoinGlass API and return as a Markdown table.

Parameters:
    coin (str): Cryptocurrency to query ('BTC' or 'ETH').

Returns:
    str: Markdown table with ETF flow data (tickers as columns, dates as rows, with total column).

ParametersJSON Schema

Name	Required	Description	Default
`coin`	Yes

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the action ('Fetch') and output format ('Markdown table'), but lacks details on error handling, rate limits, authentication needs, or data freshness. It adequately covers basic behavior but misses advanced operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded, with a clear opening sentence followed by specific sections for parameters and returns. Every sentence adds value without redundancy, making it efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (single parameter, no output schema, no annotations), the description is mostly complete. It covers purpose, parameters, and return format, but could improve by addressing behavioral aspects like error cases or data limitations, which would enhance completeness for an API-based tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds significant meaning beyond the input schema, which has 0% coverage. It explicitly defines the 'coin' parameter as a string with allowed values ('BTC' or 'ETH') and explains its purpose ('Cryptocurrency to query'), compensating fully for the schema's lack of documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Fetch'), resource ('historical ETF flow data'), and scope ('for BTC or ETH from CoinGlass API'). It distinguishes the data source and format, making the function unambiguous even without sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying the cryptocurrency options ('BTC' or 'ETH') and the data source (CoinGlass API), but it does not provide explicit guidance on when to use this tool versus alternatives or any prerequisites. Since there are no sibling tools, the lack of comparative guidance is less critical.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

1 tool updatev1.0.0Aug 14, 2025
- First observedget_etf_flow

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored 2026-04-18 10:20 across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is singular and clearly defined.

Naming Consistency5/5

The single tool name 'get_etf_flow' follows a clear verb_noun pattern. Since there are no other tools, consistency is inherently perfect.

Tool Count2/5

One tool is too few for the server's apparent scope of ETF flow data analysis. It lacks complementary tools like historical trends, comparisons, or metadata, making the surface feel thin and incomplete for the domain.

Completeness2/5

The tool set is severely incomplete for ETF flow analysis. It only fetches data for BTC or ETH, missing operations like multi-coin queries, date range filtering, summary statistics, or visualization, which are essential for comprehensive coverage.

Maintenance

ActivityInactive

ResponsivenessUnresponsive

Resources

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

mcp A
com.everstake
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
Blockchain Cryptocurrency
1111
crypto-defi-mcpOAuth
com.thenextgennexus
MCP server giving AI agents one-connection access to crypto & DeFi data: DeFi protocol TVL, stableco
Cryptocurrency Finance Blockchain
2
anotherai
dev.anotherai
MCP server for building and testing AI agents with multi-model experimentation and insights.
Agent Orchestration Autonomous Agents Testing & QA Tools
2
china-market-intelligence-mcpOAuth
com.thenextgennexus
MCP server giving AI agents one-connection access to China A-share market intelligence: financials,
Finance Research & Data
2

Related MCP Servers

crypto-sentiment-mcp
Cryptocurrency Social Media Research & Data
kukapay
A
license
A
quality
D
maintenance
An MCP server that delivers cryptocurrency sentiment analysis to AI agents.
Updated 2 years ago (2025-03-27 22:59 UTC)
5
47
MIT
crypto-portfolio-mcp
Cryptocurrency Finance Autonomous Agents
kukapay
A
license
Not graded
quality
D
maintenance
An MCP server for tracking and managing cryptocurrency portfolio allocations, enabling AI agents to query and optimize portfolio strategies in real time.
Updated 2 years ago (2025-04-05 04:11 UTC)
10
MIT
DEX Pools MCP
Blockchain Cryptocurrency Finance
kukapay
A
license
A
quality
D
maintenance
An MCP server that provides AI agents with real-time access to DEX liquidity pool data, enabling smarter trading, analytics, and automated strategies.
Updated a year ago (2025-10-01 08:54 UTC)
10
1
MIT
Crypto Funds MCP
Cryptocurrency Finance
kukapay
A
license
Not graded
quality
D
maintenance
An MCP server that provides AI agents with structured, real-time data on cryptocurrency investment funds, enabling deeper due diligence and portfolio intelligence.
Updated a year ago (2025-09-25 03:18 UTC)
3
MIT

Appeared in Searches

A server for providing crypto market history data

Flujo de ETF MCP

Características

Prerrequisitos

Instalación

Uso

Integración con Claude Desktop

Ejemplo de salida

Licencia

Available Tools

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

crypto-sentiment-mcp

crypto-portfolio-mcp

DEX Pools MCP

Crypto Funds MCP

Appeared in Searches