MCP server exposing DeFi lending yields, TVL, utilization and token prices from The Graph
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"curator-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# curator-mcp **Live DeFi lending yields, TVL, utilization and token prices on Base — as MCP tools.** An MCP server that answers the questions an agent actually asks about DeFi markets: *where should this asset sit, what does it earn, and how deep is the liquidity?* Data comes from [The Graph](https://thegraph.com) — Messari standardized subgraphs for lending and DEX markets, and the Token API for spot prices. Standalone and dependency-light. It knows nothing about any particular agent; it was extracted from one, which is the only relationship it has to the vault curator that first used it. --- ## Install Requires Python ≥ 3.10 and a free Graph API key from [thegraph.com/studio](https://thegraph.com/studio) → API Keys. ```bash uvx curator-mcp # run without installing # or pip install curator-mcp ``` Published on PyPI — no clone required. Verified from a machine that has never seen this repo. **From a clone**, if you want to modify it: ```bash git clone <this-repo> && cd <this-repo> uv pip install ./data/curator_mcp ``` ## Configure your MCP client ```jsonc { "mcpServers": { "curator": { "command": "uvx", "args": ["curator-mcp"], "env": { "GRAPH_API_KEY": "your-key-here" } } } } ``` That is the whole setup. Claude Desktop, Claude Code, Cursor, Zed and anything else speaking MCP over stdio will pick the tools up. --- ## Tools | Tool | Arguments | Answers | |---|---|---| | `compare_protocols` | `asset` | Where should this asset sit? Ranks every protocol, and names the best-APY and deepest-TVL ones separately because they are usually not the same. | | `get_market_yields` | `asset` | What does this asset earn, and where? Supply-side APYs across every protocol listing it. | | `list_markets` | `assets?` | Broad survey of lending markets and DEX pools. | | `get_token_price` | `symbol` | Spot USD price. | Plus a `curator://protocols` resource listing which protocols are configured. ### Response shape Every to…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.