yieldhunter
REMOTE · YIELDHUNTER-AGENT-PRODUCTION.UP.RAILWAY.APP
Risk-adjusted stablecoin yield ranks for other agents. Research only. Never holds keys or executes.
Available components
Last scanned (10 hours ago)
Scores higher than 85% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 29 Oct 26 0
- Server version: 1.0.4 → 1.0.5 functional
- 28 Oct 26 0
- Server version: 1.0.2 → 1.0.4 functional
- 24 Oct 26 0
- Tool “compare_opportunities” rewrote its description, which is the text the model reads security
- Tool “explain_score” rewrote its description, which is the text the model reads security
- Tool “get_protocol_risk” rewrote its description, which is the text the model reads security
- Server version: 1.0.0 → 1.0.2 functional
- “get_protocol_risk” reworded the description of “protocol” cosmetic
- “get_protocol_risk” reworded the description of “protocolSlug” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 0
- Server version: 0.1.0 → 1.0.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://yieldhunter-agent-production.up.railway.app/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of yieldhunter-agent-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yieldhunter-agent-production.up.railway.app/mcp | Unreachable | ||
| http (plaintext) | http://yieldhunter-agent-production.up.railway.app/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_opportunities Compare opportunities ~334
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 (including protocolSlug for get_protocol_risk), 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 }
| Name | Type | Req | Description |
|---|---|---|---|
| horizonDays | number | – | Holding horizon in days for gas/bridge amortization (default 30). Example: 30 |
| notionalUsd | number | – | Notional USD size for net-yield cost amortization and exitRisk TVL multiples (default 10000). Example: 10000 |
| opportunityIds | array | – | Alias for poolIds — same list_yields opportunities[].id values. |
| poolIds | array | – | 2–5 list_yields opportunities[].id values. Example: ["id-a","id-b"]. Alias: opportunityIds. |
| sourceChainKey | string | – | Agent's current chain for bridge cost estimate: ethereum | base | arbitrum (aliases: eth, ETH, Ethereum, arb, ARB, BASE). Blank/whitespace is VALIDATION_ERROR (omit the field to default). Unknown key… |
No output schema declared.
No examples provided.
explain_score Explain score ~459
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, 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), plus id and protocolSlug (same as list_yields; pass protocolSlug to get_protocol_risk). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| horizonDays | number | – | Holding horizon in days for gas/bridge amortization (default 30). Example: 30 |
| id | string | – | Same as list_yields opportunities[].id (canonical response field name). |
| notionalUsd | number | – | Notional USD size for net-yield cost amortization and exitRisk TVL multiples (default 10000). Example: 10000 |
| opportunityId | string | – | Alias for list_yields opportunities[].id (same pool key as poolId / id). |
| poolId | string | – | Alias for list_yields opportunities[].id (historical tool field). Same DefiLlama pool UUID. Example: "43641cf5-a92e-416b-bce9-27113d3c0db6" |
| sourceChainKey | string | – | Agent's current chain for bridge cost estimate: ethereum | base | arbitrum (aliases: eth, ETH, Ethereum, arb, ARB, BASE). Blank/whitespace is VALIDATION_ERROR (omit the field to default). Unknown key… |
No output schema declared.
No examples provided.
get_protocol_risk Get protocol risk ~255
Protocol-level risk card (age, audit signals, curated known issues, category, score 0–100). Chain: pass list_yields opportunities[].protocolSlug as protocol or protocolSlug. Display names also resolve case- and space-insensitively via DefiLlama protocol metadata (e.g. "Compound V3" → compound-v3, "Curve" → curve-dex, "Euler V2" → euler-v2). Unknown names return NOT_FOUND naming the field, with example {"protocolSlug":"aave-v3"} and up to 3 closest slugs. Higher score = lower protocol risk. Uses curated priors plus DefiLlama metadata when available. Research only — non-custodial. Example: { "protocol": "aave-v3" } Also accepts protocolSlug or a display name such as "Compound V3".
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | – | Protocol slug (DefiLlama project id) or display name, e.g. "aave-v3" or "Compound V3". Prefer list_yields opportunities[].protocolSlug. |
| protocolSlug | string | – | Alias for protocol — list_yields opportunities[].protocolSlug (display names also resolve). |
No output schema declared.
No examples provided.
health Health ~142
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. If yields+pegs vintage is missing or at/over YH_STALE_DEGRADE_SECONDS (default 2h), health may refresh DefiLlama market caches once (same adapters as list_yields; not a list_yields tool call). Kill switch on: health still answers, refresh skipped. Research estimates only — non-custodial; never holds keys or executes transactions. Copy-paste path starts here, then list_yields. Example input: {}
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_yields List risk-adjusted yields ~1,601
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…
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | – | Stablecoin symbols to match in pool symbol, e.g. ["USDC","USDT"] |
| categories | array | – | Include only these categories: "lending" | "rwa" | "other" |
| chainIds | array | – | Optional numeric chain ids: 1, 8453, 42161 only. Any other id is VALIDATION_ERROR (not a silent default-universe fallback). |
| chains | array | – | Filter chains: ethereum | base | arbitrum (aliases eth/ETH/Ethereum, arb/ARB, BASE; or Llama names). Default when field omitted: all three. Blank, whitespace, or unsupported values (solana, optimism,… |
| diversity | string | – | Presented top-k protocol diversity: "soft" (default, max 2 per protocol) | "off" (plain score order, every market) |
| excludeCategories | array | – | Exclude these categories, e.g. ["rwa"] |
| horizonDays | number | – | Holding horizon in days for gas/bridge amortization (default 30). Example: 30 |
| includeFactors | boolean | – | If true, each opportunity includes scores.factors compact map (protocolRisk, depegCounterparty, liquidity, yieldQuality, costAdjusted). Default false — omits heavy factors[] rationales. |
| limit | integer | – | Max results to return (default 10, max 25). Example: 10 |
| maxRewardShare | – | – | Incentive-share gate only: max reward/total of gross APY, 0–1 (e.g. 0.3 treasury, 0.25 stricter). Does not remove high base-only APY farms. Capital preservation still needs minScore/riskAppetite/excl… |
| minScore | – | – | Minimum compositeRiskAdjusted after appetite weights (0–100). Omitted = no filter |
| minTvlUsd | number | – | Minimum TVL in USD (default 1000000). Example: 5000000 |
| notionalUsd | number | – | Notional USD size for net-yield cost amortization and exitRisk TVL multiples (default 10000). Example: 10000 |
| protocols | array | – | Optional protocol slugs, e.g. ["aave-v3","morpho-blue"]. Blank entries are VALIDATION_ERROR (not treated as all protocols). |
| riskAppetite | string | – | Scoring weight profile: "balanced" (default/v1.1) | "conservative" | "aggressive" |
| sortBy | string | – | Sort key: "risk_adjusted" (default) | "net_apy" | "gross_apy" | "tvl" |
| sortOrder | string | – | Sort direction: "desc" (default) | "asc" |
| sourceChainKey | string | – | Agent's current chain for bridge cost estimate: ethereum | base | arbitrum (aliases: eth, ETH, Ethereum, arb, ARB, BASE). Blank/whitespace is VALIDATION_ERROR (omit the field to default). Unknown key… |
No output schema declared.
No examples provided.
score_opportunity Score opportunity ~482
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.
| Name | Type | Req | Description |
|---|---|---|---|
| horizonDays | number | – | Holding horizon in days for gas/bridge amortization (default 30). Example: 30 |
| id | string | – | Same as list_yields opportunities[].id (canonical response field name). |
| notionalUsd | number | – | Notional USD size for net-yield cost amortization and exitRisk TVL multiples (default 10000). Example: 10000 |
| opportunityId | string | – | Alias for list_yields opportunities[].id (same pool key as poolId / id). |
| poolId | string | – | Alias for list_yields opportunities[].id (historical tool field). Same DefiLlama pool UUID. Example: "43641cf5-a92e-416b-bce9-27113d3c0db6" |
| sourceChainKey | string | – | Agent's current chain for bridge cost estimate: ethereum | base | arbitrum (aliases: eth, ETH, Ethereum, arb, ARB, BASE). Blank/whitespace is VALIDATION_ERROR (omit the field to default). Unknown key… |
No output schema declared.
No examples provided.
How do I install the yieldhunter MCP server?
yieldhunter is a hosted endpoint at https://yieldhunter-agent-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · yieldhunter-agent-production.up.railway.app
claude mcp add --transport http agentsherpa-yieldhunter 'https://yieldhunter-agent-production.up.railway.app/mcp'
What is the yieldhunter MCP server?
yieldhunter is an MCP server listed in the public MCP registry as io.github.agentsherpa/yieldhunter. Risk-adjusted stablecoin yield ranks for other agents. Research only. Never holds keys or executes. This page covers its hosted endpoint (https://yieldhunter-agent-production.up.railway.app/mcp).
Is the yieldhunter MCP server safe to use?
yieldhunter scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the yieldhunter MCP server expose?
yieldhunter exposes 6 tools: health, list_yields, score_opportunity, compare_opportunities, explain_score, get_protocol_risk. Their descriptions and schemas cost roughly 3,273 tokens of context every time the server is loaded.
Does the yieldhunter MCP server require authentication?
Its publisher declares no required credentials for yieldhunter. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the yieldhunter MCP server still maintained?
yieldhunter is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.