yieldhunter
Risk-adjusted ranks, then a policy check.
What it can do
- Health: Liveness and capability check for yieldhunter (yieldhunter.eth). Returns service status, schemaVersion, scoringVersion, feature flags, and the list of available tools. Use this first to verify
- List Yields: Rank stablecoin yield opportunities on Ethereum, Base, and Arbitrum using multi-factor **risk-adjusted** scoring (not raw APY). chains/chainIds: those three only (aliases eth/ETH/Ethereum
- Score Opportunity: Compute the full multi-factor risk-adjusted score for a single opportunity from list_yields. Chain: pass list_yields opportunities[].id as poolId, opportunityId, or id (same DefiLla
What data it sees
Do you need an account
No: the server works without sign-in
Risk-adjusted ranks, then a policy check. Research only. yieldhunter.eth, Base 61006, not RNWY 12099.
How to connect
How to connect yieldhunter to Claude
The server address to paste into Claude settings:
https://yieldhunter--agentsherpa.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect yieldhunter to ChatGPT
The server address to paste into ChatGPT settings:
https://yieldhunter--agentsherpa.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect yieldhunter to Cursor
The server address to paste into Cursor settings:
https://yieldhunter--agentsherpa.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (6)
Raw names from tools/list. Only developers need these.
| health | Liveness and capability check for yieldhunter (yieldhunter.eth). Returns service status, schemaVersion, scoringVersion, feature flags, and the list of available tools. Use this first to verify connectivity. Research estimates only — non-custodial; never holds keys or executes transactions. Copy-paste path starts here, then list_yields. Example input: {} |
| list_yields | Rank stablecoin yield opportunities on Ethereum, Base, and Arbitrum using multi-factor **risk-adjusted** scoring (not raw APY). chains/chainIds: those three only (aliases eth/ETH/Ethereum, arb/ARB, BASE) — any unsupported or blank value (solana, optimism, "") is VALIDATION_ERROR, not a silent default-universe fallback. sourceChainKey: same keys/aliases; blank or unknown keys are VALIDATION_ERROR (bridge cost is not estimated). Default ranking is risk-adjusted score, not highest APY. For headline yield order, use sortBy=net_apy. Default is risk-adjusted ranking with balanced weights. Optional params are policy controls for visiting agents. Default when omitted: sortBy=risk_adjusted, sortOrder=desc, riskAppetite=balanced (v1.1 weights), no minScore, no category filter, diversity=soft (max 2 markets per protocol in presented top-k). Primary composite key: compositeRiskAdjusted (protocol risk, depeg/counterparty, liquidity, yield quality base vs incentive, net yield after gas/bridge). Opportunities may include stability signals: apyChange24h is pool-level DefiLlama apyPct1D when present as a number (including 0 = observed flat change); null/missing means unknown/not provided for that pool (e.g. some Pendle markets) — not the same as 0, never invent 0; tvlChange24hPct is protocol-level DefiLlama change_1d (shared across markets of the same protocol — not this pool's TVL flow; missing stays null); large APY jumps warn only. Also exitRisk/exitRiskReason (size-vs-pool liquidity heuristic only: pool TVL vs notionalUsd + liquidity confidence — not on-chain withdraw, not queue/cap/pause/lockup, not transfer whitelist/eligibility/redemption, not an execution gate; unknown ≠ safe; medium often means liquidity confidence medium, not “small pool”; low is strict; when knownIssues mention transfer/eligibility do not treat low as free exit; soft warnings on high/unknown, plus low/medium if those issues are present; does not change default risk-adjusted ranking). Optional policy knobs: sortBy (risk_adjusted|net_apy|gross_apy|tvl), sortOrder, riskAppetite (conservative|balanced|aggressive), minScore (0–100 after appetite; practical bands ~≥85 treasury default, ≥80 selective; 90 is rare/very strict — a few top L2 blue-chips may clear it), categories / excludeCategories (lending|rwa|other), diversity (soft|off — default top prefers protocol diversity; set off for every market from one protocol), includeFactors (boolean, default false — when true each opportunity has scores.factors compact map without a second tool call), maxRewardShare (0–1 optional incentive-share gate only — max reward/total; e.g. 0.3 treasury, 0.25 stricter; unknown share excluded when set; does not remove high base-only APY farms — pair with minScore/riskAppetite/excludeCategories for capital preservation). Prefer this when capital preservation and sustainable yield matter more than headline APY. Research only — never executes transactions or holds keys. Copy-paste path (after health {}): { "assets": ["USDC"], "sortBy": "risk_adjusted" } Then contrast #1 vs #2 (risk-adjusted winner vs next row — often higher rate / thinner liquidity / other chain). Do not contrast against the max-APY row in the ten. Examples: (a) Treasury/conservative: { "riskAppetite": "conservative", "minScore": 85, "excludeCategories": ["rwa"], "maxRewardShare": 0.3, "minTvlUsd": 10000000, "limit": 10 } (b) Default research (v1.1): { "assets": ["USDC"], "sortBy": "risk_adjusted" } (c) Yield-seeking: { "sortBy": "net_apy", "riskAppetite": "aggressive", "chains": ["base"], "assets": ["USDC"], "limit": 15 } (d) With factor breakdown: { "assets": ["USDC"], "limit": 5, "includeFactors": true } |
| score_opportunity | Compute the full multi-factor risk-adjusted score for a single opportunity from list_yields. Chain: pass list_yields opportunities[].id as poolId, opportunityId, or id (same DefiLlama pool UUID; id is the canonical list field). Returns APY breakdown (base/reward/total), factor scores with rationales, net yield after gas/bridge, exitRisk heuristic (TVL vs notional + liq conf only; medium ≠ small pool; not queues/caps/transfer whitelist/eligibility/on-chain withdraw; do not treat low as free exit when knownIssues mention transfer/eligibility), warnings, and sources. sourceChainKey is ethereum|base|arbitrum only — unknown keys (foo, solana) are VALIDATION_ERROR; no invented bridge fee. Research estimates only — non-custodial. Example (any one id field): { "id": "43641cf5-a92e-416b-bce9-27113d3c0db6", "horizonDays": 30, "notionalUsd": 10000 } Also accepts poolId or opportunityId with the same value. |
| compare_opportunities | Side-by-side comparison of 2–5 opportunities by risk-adjusted score. Pass list_yields opportunities[].id values as poolIds or opportunityIds. Returns ranked list, compact comparison table fields, winnerId, and rationale bullets (including when raw APY leader differs from risk-adjusted winner). sourceChainKey is ethereum|base|arbitrum only (unknown → VALIDATION_ERROR; no invented bridge fee). Research only — non-custodial. Example: { "poolIds": ["pool-id-a", "pool-id-b", "pool-id-c"], "horizonDays": 30 } |
| explain_score | Agent-readable explanation of why an opportunity received its risk-adjusted score. Chain: pass list_yields opportunities[].id as poolId, opportunityId, or id (aliases for the same key). Returns a summary paragraph, factor bullets with weighted contributions, net-yield notes, and an exitRisk heuristic line (liquidity-only — not on-chain withdraw or transfer/eligibility; medium often confidence-driven, not pool size; extra bullet when knownIssues note transfer restrictions). sourceChainKey is ethereum|base|arbitrum only (unknown → VALIDATION_ERROR; no invented bridge fee). Prefer this when you need to justify a ranking to a human or another agent. Research only — non-custodial. Example: { "opportunityId": "43641cf5-a92e-416b-bce9-27113d3c0db6", "horizonDays": 30 } Also accepts poolId or id with the same value. |
| get_protocol_risk | Protocol-level risk card (age, audit signals, curated known issues, category, score 0–100). Chain: pass list_yields opportunities[].protocolSlug as protocol or protocolSlug. Higher score = lower protocol risk. Uses curated priors plus DefiLlama metadata when available. Research only — non-custodial. Example: { "protocol": "aave-v3" } Also accepts protocolSlug. |