mcpbeat Sign in

yieldsentinel MCP Server

by agentsherpa Your server? Claim it
answering

yieldsentinel is answering right now. Last checked moments ago. It exposes 2 tools. Last commit 14 Oct 2026.

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

Uptime history 78 days of history · worst day 97%
78 days agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
219 ms
Response time
average over 24h
0
Stars
last commit 14 Oct 2026

What changed 12

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 September 2026. No other catalogue keeps this.

28 Oct a tool changed version
27 Oct a tool changed version3 times that day
27 Oct a tool description was rewritten health
23 Oct a tool changed the parameters it asks for check_position
23 Oct a tool description was rewritten check_position
23 Oct a tool changed version
13 Sep 2 tools changed the parameters they ask for3 times that day check_position, health
12 Sep a tool description was rewritten health
and 3 more, back to 12 September 2026

Nothing serious here today

Today is the operative word: we check yieldsentinel every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add yieldsentinel --transport http https://yieldsentinel-agent-production.up.railway.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://yieldsentinel-agent-production.up.railway.app/mcp
~/.codex/config.toml
[mcp_servers.yieldsentinel]
url = "https://yieldsentinel-agent-production.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "yieldsentinel": {
      "url": "https://yieldsentinel-agent-production.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "yieldsentinel": {
      "type": "http",
      "url": "https://yieldsentinel-agent-production.up.railway.app/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

health
health
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: {}
position
check_position
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 }

Endpoints

URLTransportStateLatencyChecked
https://yieldsentinel-agent-production.up.railway.app/mcp streamable-http answering 268 ms 0 min ago

Alternatives to yieldsentinel

same job, measured the same way
Ribcage Agent Services
by jrcage

Verification and research desk for agents: packet validation, token screens, settlement checks.

42 installs/wk local only
Tue Christensen
by tuechristensen

Learn about Tue Christensen's operations-research work or describe an OR problem to him.

6 tools answering
TanStarter Docs
by mkfasthq

Search published TanStarter documentation. Read-only and public.

1 tools answering
yieldhunter
by agentsherpa

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

6 tools answering
Riptide — public risk and event research
by beepboop2025

Read-only paper risk evidence and policy-gated committed event research. No real orders.

answering
Verateca
by a1476

Dietary supplement register: compositions, country upper limits, US prices, stack check vs limits.

6 tools answering
Returnolio
by returnolio

Read-only stock research: company scores, the Monthly Top 10, the screener and your own portfolio.

answering
Traditional Chinese (zh-TW) Taiwan Community Forum
by shuaigle

Search & read a zh-TW Taiwan community forum (PTT-style); AI agents can register to post & comment.

13 tools answering

yieldsentinel — questions

Answers built from our own checks of this server.

What can yieldsentinel do?
It exposes 2 tools, read directly from the server on our last check. Among them: check_position, health. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is yieldsentinel working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 219 ms. The bar chart above shows every period we have measured.
How do I connect yieldsentinel?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does yieldsentinel need an API key?
No. yieldsentinel completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is yieldsentinel?
It answers our handshake in 219 ms on average, which is faster than 64% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is yieldsentinel open source?
The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at yieldsentinel-agent-production.up.railway.app, which runs on its operator's own terms.