DeFi Yields MCP
An MCP server for AI agents to explore DeFi yield opportunities, powered by DefiLlama.
Features
- Data Fetching Tool: The
get_yield_poolstool retrieves DeFi yield pool data from the DefiLlama, allowing filtering by chain (e.g., Ethereum, Solana) or project (e.g., Lido, Aave). - Analysis Prompt: The
analyze_yieldsprompt generates tailored instructions for AI agents to analyze yield pool data, focusing on key metrics like APY, 30-day mean APY, and predictions. - Packaged for Ease: Run the server directly with
uvx defi-yields-mcp.
Installation
To use the server with Claude Desktop, you can either install it automatically or manually configure the Claude Desktop configuration file.
Option 1: Automatic Installation
Install the server for Claude Desktop:
uvx mcp install -m defi_yields_mcp --name "DeFi Yields Server"
Option 2: Manual Configuration
Locate the configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Add the server configuration:
{
"mcpServers": {
"defi-yields-mcp": {
"command": "uvx",
"args": [ "defi-yields-mcp" ]
}
}
}
Restart Claude Desktop.
Examples
You can use commands like:
- "Fetch yield pools for the Lido project."
- "Analyze yield pools on Ethereum."
- "What are the 30-day mean APYs for Solana pools?"
The get_yield_pools tool fetches and filters the data, while the analyze_yields prompt guides the LLM to provide a detailed analysis.
Example Output
Running the get_yield_pools tool with a filter for Ethereum:
[
{
"chain": "Ethereum",
"pool": "STETH",
"project": "lido",
"tvlUsd": 14804019222,
"apy": 2.722,
"apyMean30d": 3.00669,
"predictions": {
"predictedClass": "Stable/Up",
"predictedProbability": 75,
"binnedConfidence": 3
}
},
...
]
License
This project is licensed under the MIT License. See the LICENSE file for details.
Metadata
Release files for iflow-mcp_defi-yields-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_defi_yields_mcp-0.1.0.tar.gz | 17.6 kB | Without provenance | Details for iflow_mcp_defi_yields_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_defi_yields_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_defi_yields_mcp-0.1.0-py3-none-any.whl |
Total release size: 22.3 kB
Release files / iflow_mcp_defi_yields_mcp-0.1.0.tar.gz
| Download URL | iflow_mcp_defi_yields_mcp-0.1.0.tar.gz |
|---|---|
| Size | 17.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
66e783751a243fad7b4b8b0a46ffcd9f9ef73f9b8e1bd2a9b198cec6b15046a6
|
|
BLAKE2b-256 checksum How to use checksums |
c120496ef1dbd788efd5fc0bbc062d8420f4df08b887877e52aafee5af273dcc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.9
|
Release files / iflow_mcp_defi_yields_mcp-0.1.0-py3-none-any.whl
| Download URL | iflow_mcp_defi_yields_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33f907e2c67b89f07c55a106154d726619ee821e12ae01344e6c6ebd37782179
|
|
BLAKE2b-256 checksum How to use checksums |
cf0d6905e95ed96b7fbd3e11bd1897db36ae1e69063e876f1d131d298479eabf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.9
|
Security for iflow-mcp_defi-yields-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.