defi-yield-engine
https://defi-yield-engine-production.up.railway.app
Registry code: 0c782e75f2aa9976
Risk-adjusted DeFi yield recommendations powered by DeFiLlama. Use get_best_yield to find the optimal yield for a given asset and risk profile. Use explain_risk to understand why a protocol is rated as it is. Use compare_yields to compare multiple protocols side-by-side. All outputs are optimized for minimal token consumption.
- endpoint
- https://defi-yield-engine-production.up.railway.app/mcp
- door code
- 8dc70f624af7f609
- protocol
- JSONRPC ·0.2
- authentication
- x402
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is defi-yield-engine live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
- Is defi-yield-engine free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does defi-yield-engine have?
- 12 tools: Explain Protocol Risk, Get Best Liquid Staking, Get Best RWA Protocol, Get Best DeFi Yield, Get Perps Overview, Compare Perps Protocols, Check Yield Alert, Get Best Restaking / LRT, ….
- Is defi-yield-engine safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.5%· all time 99.1%
last good check
of 12 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- find the best defi yield for an asset
- compare defi protocols by risk
- get optimal yield allocation
- score a smart contract for risk
- set an apy alert
- takes → gives
- text, data → data
- tools
- 11 reads1 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred from the card: no interface answered anonymously and the card declares security schemes
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
explain_risk reads auth-required never probed
9-signal risk breakdown for any DeFiLlama protocol.
get_best_liquid_staking reads auth-required never probed
Best LST protocol for ETH, SOL, BNB. Covers Lido, Rocket Pool, Jito, 50+ others.
get_best_rwa reads auth-required never probed
Top Real World Asset protocols: T-bills (Ondo, BUIDL), private credit (Maple, Centrifuge).
get_best_yield reads auth-required never probed
Single best risk-adjusted yield for USDC, USDT, ETH across 548 protocols.
get_perps_overview reads auth-required never probed
Top perpetuals by 24h volume: Hyperliquid, dYdX, GMX, Drift, Jupiter Perps.
compare_perps reads auth-required never probed
Side-by-side comparison of perpetuals protocols by volume.
yield_alert_check reads auth-required never probed
Poll alert status — triggered/watching + current best APY.
get_best_restaking reads auth-required never probed
Best restaking (EigenLayer, Symbiotic) or liquid restaking token (Ether.fi, Renzo, Puffer).
get_optimal_allocation reads auth-required never probed
Split capital across 2-5 protocols for maximum risk-adjusted yield.
compare_yields reads auth-required never probed
Side-by-side risk-adjusted comparison of 2-6 protocols.
get_defi_overview reads auth-required never probed
Free snapshot: top protocols across Yield, Staking, Restaking, RWA and Perps.
yield_alert_set changes data auth-required never probed
Register APY threshold alert — fires when yield exceeds target.
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id0c782e75f2aa9976.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/0c782e75f2aa9976/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/0c782e75f2aa9976?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.