# yieldhunter (remote · yieldhunter-agent-production.up.railway.app)

Risk-adjusted stablecoin yield ranks for other agents. Research only. Never holds keys or executes.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `yieldhunter-agent-production.up.railway.app`: 82/100 (this document), [markdown](https://verifymcp.io/servers/agentsherpa-yieldhunter/yieldhunter-agent-production.md), [page](https://verifymcp.io/servers/agentsherpa-yieldhunter/yieldhunter-agent-production)

## Channel facts

- Endpoint: `https://yieldhunter-agent-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3357 tokens (~559/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http agentsherpa-yieldhunter 'https://yieldhunter-agent-production.up.railway.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "agentsherpa-yieldhunter": {
      "url": "https://yieldhunter-agent-production.up.railway.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "agentsherpa-yieldhunter": {
      "type": "http",
      "url": "https://yieldhunter-agent-production.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.agentsherpa-yieldhunter]
url = "https://yieldhunter-agent-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agentsherpa-yieldhunter": {
      "type": "remote",
      "url": "https://yieldhunter-agent-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add agentsherpa-yieldhunter --url 'https://yieldhunter-agent-production.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  agentsherpa-yieldhunter:
    url: "https://yieldhunter-agent-production.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "agentsherpa-yieldhunter": {
      "Transport": "http",
      "Url": "https://yieldhunter-agent-production.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add agentsherpa-yieldhunter -t streamable-http -u 'https://yieldhunter-agent-production.up.railway.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "agentsherpa-yieldhunter": {
      "type": "http",
      "url": "https://yieldhunter-agent-production.up.railway.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 79, +1)

- [functional] Server version: 0.1.0 → 1.0.0

### 2026-09-13 (score 78, 0)

- [security] Tool “health” rewrote its description, which is the text the model reads

### 2026-09-11 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `health` (~142 tokens)

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. 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: {}

### `list_yields` (~1601 tokens)

List risk-adjusted 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…

Input parameters:

- `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…

### `score_opportunity` (~482 tokens)

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.

Input parameters:

- `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…

### `compare_opportunities` (~325 tokens)

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
}

Input parameters:

- `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…

### `explain_score` (~439 tokens)

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.

Input parameters:

- `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…

### `get_protocol_risk` (~150 tokens)

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.

Input parameters:

- `protocol` (string): Protocol slug (DefiLlama project id), e.g. "aave-v3". Same as list_yields opportunities[].protocolSlug.
- `protocolSlug` (string): Alias for protocol — list_yields opportunities[].protocolSlug.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/agentsherpa-yieldhunter/yieldhunter-agent-production#diagnostics

## Score history

- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 77
- 2026-09-09: 77
- 2026-09-08: 76
- 2026-09-07: 76
- 2026-09-06: 75
- 2026-09-05: 75
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 74
- 2026-09-01: 73
- 2026-08-31: 73
- 2026-08-30: 72
- 2026-08-29: 72
- 2026-08-28: 71
- 2026-08-27: 71
- 2026-08-26: 70
- 2026-08-25: 68
- 2026-08-24: 68
- 2026-08-23: 67
- 2026-08-22: 67

## Common questions

### 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,139 tokens of context every time the server is loaded.

### Does the yieldhunter MCP server require authentication?

No. We connected to yieldhunter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the yieldhunter MCP server still maintained?

yieldhunter is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://yieldhunter-agent-production.up.railway.app/mcp
- Repository: https://github.com/agentsherpa/yieldhunter-connect
- Website: https://yieldhunter-agent-production.up.railway.app/
- Changelog RSS feed: https://verifymcp.io/servers/agentsherpa-yieldhunter/yieldhunter-agent-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/agentsherpa-yieldhunter/yieldhunter-agent-production.json
- HTML version of this page: https://verifymcp.io/servers/agentsherpa-yieldhunter/yieldhunter-agent-production