Sato Hub
MCP

Yield.xyz AgentKit (MCP + x402)

Non-custodial onchain yield API for agents: discover, assess, enter and exit 3,300+ staking/lending/RWA yields over one MCP server, paid per call via x402.

  • Sato Score64
  • ChainsBase, Ethereum +4
ActiveSelf-Reported

Yield.xyz AgentKit (MCP + x402) is a closed-source MCP server on Base, Ethereum, Solana and other chains, with no code activity tracked. Sato Score 64/100 (how open, active and verifiable it is, not a safety grade), as of 2026-11-07. How the score works →

Check what an install would ask of your keys, before you run it →

No code activity tracked

Listed from yield.xyz on 2026-09-23. Install: not attempted — no install path on record. Evidence →

Next step

Watch Yield.xyz AgentKit (MCP + x402)

One email if what we observe changes — its endpoint stops answering, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on https://mcp.yield.xyz/mcp before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Yield.xyz launched AgentKit on x402 on 2026-07-30. It exposes its yield API as one MCP server that agents can call without an API key, paying in USDC on Base through the CDP facilitator (CoinbaseDev on X). The live manifest at mcp.yield.xyz/.well-known/x402 lists tools including yields_get, yields_get_risk, actions_enter, actions_exit and actions_manage. The docs describe it as an API for non-custodial staking, restaking, liquid staking, lending, RWA yields and vaults across 70-80+ networks. Execution stays non-custodial: the API returns actions and the agent signs them.

Sato Score

64/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
0/20
Interface verifiability
10/10
Docs & demo
6/10
Listing transparency & provenance
6/15
Independent verification
7/10

Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).

Evidence — listed vs checked · what the words mean

Listed from yield.xyz on 2026-09-23. Install: not attempted — no install path on record.

ClaimValueEvidenceSourceChecked
Chains supportedBase, Ethereum, Solana, Cosmos, Tron, Multichainself-reporteddocs.yield.xyzas of 2026-11-07
Verification statusSelf-Reported — not independently reviewedself-reportedyield.xyzas of 2026-11-07
MCP endpoint answersanswered — 22 tools listedobservedmcp.yield.xyz2026-11-07
Daily check record45 of 45 daily checks since 2026-09-23 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-11-06
ERC-8004 registrationdeclared address not found in the registryobserved—2026-11-07
Sato Score64/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-11-07

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Tool inventory — 22 tools, probed live 2026-11-07

  • yields_get_all — Discover yield opportunities across all supported networks and protocols. Use this to find yield IDs before calling yields_get, actions_enter, or any balance/validator tools. Filter by network, token
  • yields_get — Get full metadata for a single yield opportunity: fees, lock-up and cooldown periods, reward mechanics, and whether entry/exit is currently open. Show this to the user before they commit to entering a
  • yields_get_validators — List validators for delegation-based yields such as Cosmos native staking or ETH native staking. Use the validator address when calling actions_enter or actions_exit. Filter by preferred=true to show
  • yields_get_balances — Get current balances and pending actions for a wallet address across one or more yields. Always call this before actions_exit or actions_manage — the passthrough value required by those tools comes fr
  • actions_enter — Construct unsigned transactions to stake or deposit into a yield. Does NOT execute — the user must sign each transaction exactly as returned (never modify unsignedTransaction). Amounts are human-reada
  • actions_exit — Construct unsigned transactions to unstake or withdraw from a yield. Does NOT execute — the user must sign each transaction exactly as returned (never modify unsignedTransaction). Amounts are human-re
  • actions_manage — Construct unsigned transactions for a pending action such as claiming rewards, restaking, or unlocking funds. Does NOT execute — the user must sign. The action type and passthrough must come from yiel
  • submit_hash — Submit the on-chain transaction hash after the user has signed and broadcasted a transaction. This updates the transaction status internally and enables tracking. Call this once per transaction, using
  • get_transaction — Poll the status of a single transaction by its ID. Use after submit_hash to confirm on-chain success. status is one of: NOT_FOUND, CREATED, BLOCKED, WAITING_FOR_SIGNATURE, SIGNED, BROADCASTED, PENDING
  • actions_get — Get the current status and transactions of a specific action by its ID. Use this to check whether an action is CREATED, PROCESSING, SUCCESS, or FAILED. Essential for async execution patterns and semi-
  • actions_get_all — List past and pending actions for a wallet address. Filter by status, intent, type, or yieldId. Use this to answer "show me my pending actions", "what did I do recently?", or to find actions waiting f
  • networks_get_all — Discover all supported networks with their IDs, names, and categories. Use this to get valid network slugs before calling yields_get_all, yields_get_balances, or any other tool that requires a network
  • yields_get_reward_rate_history — Get historical APY/reward rate snapshots for a yield over time. Use this to answer "has this yield's APY been stable?" or to chart APY trends. Defaults to last 30 days, daily interval.
  • yields_get_tvl_history — Get historical Total Value Locked snapshots for a yield. Use this to assess protocol health — a declining TVL is a warning sign. Defaults to last 30 days, daily interval.
  • yields_get_risk — Get detailed risk parameters for a yield. More granular than the risk field in yields_get — returns individual risk items by category (e.g. smart contract, liquidity, counterparty). Use this when the
  • providers_get_all — Discover all supported protocols and validator providers (e.g. Lido, Aave, Morpho). Returns name, id, description, website, TVL, and type. Use this to answer "what protocols does Yield.xyz support?" o
  • yields_get_kyc_status — Get the normalized KYC status of a wallet address for a yield. Use this before actions_enter on yields that gate deposits behind KYC (e.g. RWAs like Securitize/Superstate). Yields without a KYC requir
  • yield_get_api_spec — BUILDER TOOL — fetches the live Yield.xyz OpenAPI spec (https://api.yield.xyz/docs.json). Use when you need: exact request body schemas, field constraints (min/max/enum), error response shapes, or ope
  • yield_lookup_docs — BUILDER TOOL — use when developing an integration, NOT for end-user actions or live data. Searches the live Yield.xyz documentation index (llms.txt) in real time and returns the most relevant page lin
  • yield_fetch_doc — BUILDER TOOL — fetches the full markdown content of any Yield.xyz documentation page. Use after yield_lookup_docs returns a URL. Returns authoritative spec with exact field names, types, and examples.
  • yield_troubleshoot_error — Diagnoses API errors, HTTP status codes, or unexpected responses from the Yield.xyz API. Use when developer says: "I'm getting a 422", "400 error", "rate limited", "transaction failed", "FAILED status
  • yield_list_repos — BUILDER TOOL — public Yield.xyz GitHub repos to use as a code reference for integrations. Use this when you are stuck on an integration and the other docs tools (yield_lookup_docs, yield_fetch_doc, yi
Answers a handshake
yes · 2026-11-07
Answers a call
not asked — no read-named tool takes zero arguments and declares none that touch keys, addresses or amounts

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

Observed record — 46 daily checks since 2026-09-23

100%of 46 checks since 2026-09-23 succeeded
Currently responding for 46 days
Succeeded
46
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden.

Last 30 days — to 2026-11-07, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
22
from the server's own tools/list · 29/30 days
Sato Score
64
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Base, Ethereum, Solana, Cosmos, Tron, Multichain
Agent types
MCP Server, Yield Agent
Open source
No
Last checked
2026-11-07

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#mcp#x402#defi#yield#staking#non-custodial
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Yield.xyz AgentKit (MCP + x402)'s listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Sep 23, 2026
    Listed on Sato Hub
  2. Sep 23, 2026
    Sato Hub began tracking this listing

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Yield.xyz AgentKit (MCP + x402)

Is Yield.xyz AgentKit (MCP + x402) open source?
No. Yield.xyz AgentKit (MCP + x402) is closed source as of 2026-11-07.
Which chains does Yield.xyz AgentKit (MCP + x402) support?
Yield.xyz AgentKit (MCP + x402) lists support for Base, Ethereum, Solana, Cosmos, Tron, Multichain as of 2026-11-07.
Is Yield.xyz AgentKit (MCP + x402) still maintained?
Sato Hub tracks no commit or release for Yield.xyz AgentKit (MCP + x402); it cannot say whether it is maintained.
How do I install or run Yield.xyz AgentKit (MCP + x402)?
Sato Hub has no deploy spec for Yield.xyz AgentKit (MCP + x402); follow the project's own documentation at https://docs.yield.xyz.
Is Yield.xyz AgentKit (MCP + x402) verified on Sato Hub?
Sato Hub holds one earned check for Yield.xyz AgentKit (MCP + x402): Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 64 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Yield.xyz AgentKit (MCP + x402) — Sato Hub." Sato Hub, updated 2026-11-07, accessed 2026-11-07. https://satohub.ai/resources/yield-xyz-agentkit

Data last refreshed 2026-11-07; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.