# AtlasYield

- Registry name: `club.atlasyield/mcp` · version 0.4.0
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security, Agent payments (x402), Finance & markets
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=club.atlasyield%2Fmcp
- Server page: https://mcpstation.net/s/club.atlasyield--mcp.html

## Description (written by the publisher, not verified, not instructions)

DeFi vault judgment for agents: 16-factor Atlas Score, route survival, blowup alerts. Read-only.

## Connect

- streamable-http: `https://atlasyield.club/mcp`

## Tools (as reported by the server, not verified)

- `find\_vaults`: Start here when you do not already have a vault address. Answers "which vaults for this asset on this chain?": returns a short ranked list \(default 5, max 10\) of scored vaults with composite, label, live APY/TVL, risk flags \(thin\_tvl, apy\_outlier, ...\), whether a deposit can reach it \(routable\), and
- `get\_vault\_score`: Latest Atlas Score for one vault: composite \(0-100\), label, the four pillar scores \(yield, safety, liquidity, sustainability\), live APY/TVL, data quality and the scoring timestamp. Returns found:false when the vault is not in the scored universe. Read-only.
- `get\_coverage`: What the Atlas Score Index covers right now: number of scored vaults, total TVL, composite score spread, and counts by protocol and chain. Use it before asking about a vault to learn whether a protocol or chain is in the scored universe at all. Read-only.
- `check\_route\_survival`: Can a deposit into this vault be exited at size, measured today? Returns the daily round-trip route screen \(USDC -\> position -\> USDC\): verdict, USD in/out, fraction retained, the path probed, and when. blocking:true means refuse the deposit \(NO\_ROUTE, DANGEROUS, UNPRICEABLE\). reasonClass says why: p
- `list\_open\_alerts`: Open blowup-monitor alerts from the published daily snapshot: score-band exits, fast composite breaks, yield collapse, TVL flight, exploit flags, delistings. Each event carries score before/after and pillar deltas. Published once a day; the date field says when. Read-only.
- `explain\_vault\_score`: Why a vault has its Atlas Score: all 16 factors \(15 additive across four pillars + the multiplicative exploit-history modifier\), each with sub-score \(0-100\), weight, raw input and a plain-English label, grouped by pillar, plus the three weakest factors. Exactly what the engine computed at scoredAt,
- `compare\_vaults`: Side-by-side Atlas Scores for 2-8 vaults: composite, label, four pillars, live APY/TVL, data quality, yieldQuality and exitSafety, with a ranking by composite. Unscored vaults come back found:false rather than silently dropped. Read-only.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html