yieldsentinel MCP server

• check_positionFree

  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 poolId from yieldhunter list_yields opportunities[].id (also accepted as opportunityId or id). That id is one market. 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 }

• healthFree

  Liveness and capability check for yieldsentinel (yieldsentinel.eth). Returns service status, package version, health schemaVersion (separate from the tool-envelope schemaVersion), policyVersion, feature flags, and the list of available tools. toolStats counts all origins. toolStatsExternal is the external bucket. toolStatsInternal is the internal-test bucket. Send header X-YHYS-Test: 1 on every request (initialize, notifications, and each tools/call). On this stateless server that header is the only working internal-test marker. clientInfo.name prefixes yhys-qa / yhys-feel count only for the same request they appear in. 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: {}

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1077ms20/20
• Tool poisoning2 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 18 days ago15/15
• Maintainer identityregistry namespace matches repository owner6/10

Safety score

88/100

higher than 75% of 48,255 servers

Tools

2

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

86 ms

faster than 87% of 30,031 servers

yieldsentinel: common questions

Is yieldsentinel MCP server safe?

Yes, by our scan: it is graded A (88/100). Read the yieldsentinel safety report

How do I install yieldsentinel?

It runs remotely at yieldsentinel-agent-production.up.railway.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does yieldsentinel need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is yieldsentinel maintained?

The last commit was 21 days ago (2026-10-14). The latest release is v1.0.0.

Is yieldsentinel up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does yieldsentinel compare with other MCP servers?

safety score 88/100 (higher than 75% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.