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

Policy check on a described yield position. Complement to yieldhunter. Research only.

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

## Components

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

## Channel facts

- Endpoint: `https://yieldsentinel-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-22.

- **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**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 882 tokens (~441/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 yieldsentinel MCP server?

yieldsentinel is a hosted endpoint at https://yieldsentinel-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-yieldsentinel 'https://yieldsentinel-agent-production.up.railway.app/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "agentsherpa-yieldsentinel": {
      "type": "http",
      "url": "https://yieldsentinel-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-21 (score 82, +1)

- [security] Stability: 0.97 → pass

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

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

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

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

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

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

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

- [security] Tool “health” rewrote its description, which is the text the model reads
- [functional] Schema quality: excellent → good

### 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 (2)

### `health` (~119 tokens)

Health

Liveness and capability check for yieldsentinel (yieldsentinel.eth).

Returns service status, schemaVersion, policyVersion, feature flags, and the list of available tools.

May refresh research vintage via a yieldhunter health ping; a verdict still requires check_position. YH healthy ≠ YS ok.

Use this first to verify connectivity, then call check_position with policyPreset treasury-conservative | balanced-research | rwa-selective (or explicit thresholds). Research estimates only — non-custodial; never holds keys or executes transactions.

Example input: {}

### `check_position` (~707 tokens)

Check position (research policy)

Evaluate a described stablecoin yield position against a research policy (pull).

Always pass your policy rules (or a preset). Without a policy, no meaningful check is possible — the verdict will be review/unknown, never ok.

Pass a yieldhunter opportunity id (poolId / opportunityId / id) or protocolSlug. Required for a real check: policyPreset (treasury-conservative | balanced-research | rwa-selective) and/or minScore / maxRewardShare / excludeCategories / maxExitRisk / requireCurated. Presets: treasury-conservative | balanced-research | rwa-selective. rwa-selective does not exclude RWA but is not a free pass (YS policy allowlist + higher bar). requireCurated uses the Yieldsentinel policy allowlist (curated.json), not yieldhunter scoring priors. Scoring ≠ policy approval.

Fetches live yieldhunter research (score, APY, TVL, category, rewardShare, exitRisk) and curated flags, then returns a PolicyVerdict plus A2H (summary, suggestedNextSteps, legend).

Incomplete or missing data is review/unknown — never a silent ok. A verdict is not an exit signal or execution order. Research only — never holds keys.

Example:
{ "poolId": "43641cf5-a92e-416b-bce9-27113d3c0db6", "policyPreset": "treasury-conservative", "notionalUsd": 10000 }

Input parameters:

- `asset`: Stablecoin symbol, e.g. "USDC".
- `chain`: ethereum | base | arbitrum
- `excludeCategories`: Exclude categories, e.g. ["rwa"].
- `horizonDays`: Holding horizon in days for net-yield context (default 30).
- `id`: Same as yieldhunter opportunities[].id.
- `maxExitRisk`: Cap on yieldhunter exitRisk heuristic: low | medium | high. Unknown or above the cap → review.
- `maxRewardShare`: Maximum incentive share of gross APY (0–1).
- `minNetApy`: Minimum net APY estimate.
- `minProtocolScore`: Minimum yieldhunter protocol risk score (0–100, higher = safer).
- `minScore`: Minimum compositeRiskAdjusted (0–100).
- `minTvlUsd`: Minimum pool TVL in USD.
- `notionalUsd`: Research notional in USD (size hint only). Example: 10000
- `opportunityId`: Alias for poolId / id.
- `policyPreset`: Policy preset: "treasury-conservative" | "balanced-research" | "rwa-selective". treasury-conservative excludes RWA; rwa-selective allows RWA but is not a free pass (YS policy allowlist + higher bar).
- `poolId`: yieldhunter opportunities[].id (DefiLlama pool UUID). Example: "43641cf5-a92e-416b-bce9-27113d3c0db6"
- `protocolSlug`: Protocol slug, e.g. "aave-v3".
- `requireCurated`: If true, the protocol/pool must be on the Yieldsentinel policy allowlist (curated.json), not yieldhunter scoring priors. Missing allowlist entry → review. Scoring ≠ policy approval.
- `riskAppetite`: conservative | balanced | aggressive (research posture only).

## Diagnostics

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

## Score history

- 2026-09-22: 82
- 2026-09-21: 82
- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 78
- 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: 73
- 2026-09-01: 73
- 2026-08-31: 72
- 2026-08-30: 72
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 71
- 2026-08-26: 70
- 2026-08-25: 68
- 2026-08-24: 67

## Common questions

### What is the yieldsentinel MCP server?

yieldsentinel is an MCP server listed in the public MCP registry as io.github.agentsherpa/yieldsentinel. Policy check on a described yield position. Complement to yieldhunter. Research only. This page covers its hosted endpoint (https://yieldsentinel-agent-production.up.railway.app/mcp).

### Is the yieldsentinel MCP server safe to use?

yieldsentinel 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 yieldsentinel MCP server expose?

yieldsentinel exposes 2 tools: health, check_position. Their descriptions and schemas cost roughly 826 tokens of context every time the server is loaded.

### Does the yieldsentinel MCP server require authentication?

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

### Is the yieldsentinel MCP server still maintained?

yieldsentinel is still listed as active in the MCP registry. We last reached this channel on 22 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://yieldsentinel-agent-production.up.railway.app/mcp
- Repository: https://github.com/agentsherpa/yieldsentinel-connect
- Website: https://yieldsentinel-agent-production.up.railway.app/
- Changelog RSS feed: https://verifymcp.io/servers/agentsherpa-yieldsentinel/yieldsentinel-agent-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/agentsherpa-yieldsentinel/yieldsentinel-agent-production.json
- HTML version of this page: https://verifymcp.io/servers/agentsherpa-yieldsentinel/yieldsentinel-agent-production