All servers / Web3 / AtlasYield
AtlasYield
DeFi vault judgment for agents: 16-factor Atlas Score, route survival, blowup alerts. Read-only.
Tested by ConnectATD Hosted serverTested 2026-11-22. Address: https://atlasyield.club/mcp · Registry name: club.atlasyield/mcp
Score 100 out of 100. Tested 2026-11-22.
Score breakdown
| Connects and stays up | 20 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Inputs explained | 15 / 15 | |
| Speed | 15 / 15 | |
| Safety basics | 15 / 15 | |
| Upkeep | 15 / 15 |
What we saw
- Connects and answers the MCP handshake: yes (0.3 seconds)
- Uses an encrypted (https) connection: yes
- Server reports itself as: atlasyield 0.5.0
- Tools offered: 7 · Parameters with a plain description: 19 of 19
- One safe, read-only test call to
find_vaults: worked (first call 0.7 seconds, repeat calls 0.4 seconds) - Official registry entry last updated: 2026-11-19
From the publisher
- No notes.
How hosted servers are graded
Hosted servers run on the publisher's own machines, so we cannot score downloads or install safety. We use six checks instead (connects and stays up 20, tool descriptions 20, inputs explained 15, speed 15, safety basics 15, upkeep 15). Speed is the first call to a safe, read-only tool (when a server marks none, the time to connect and list its tools), using a fresh request where we can so a saved answer cannot hide a slow one. We never call tools that write data or cost money. A server that needs a login or key is not graded. Full method.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions.
find_vaults8 of 8 parameters describedStart 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, no_yield, ...), whether a deposit can reach it (routable), and a citable page URL. It also returns what the filters REMOVED: counts per filter, the best-ranked dropped vaults with reasons, near-miss asset symbols, and whether more matched than were returned. Vaults with no deposit route and rows scored on fallback data are excluded. Ranked by the chosen metric, a ranking and not a recommendation. A flag is a caution, not a verdict, and no flag does not mean safe. Take a chosen vaultId/address to check_route_survival before any deposit. Read-only.
get_vault_score2 of 2 parameters describedLatest 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. Each vault also carries holdingsScore: the score from what it holds, with its cap; published:false means it is not yet the headline composite. notYieldProduct: true means it earns essentially nothing; do not present the score as a reason to deposit for yield. Returns found:false when the vault is not in the scored universe. Read-only.
get_coverage2 of 2 parameters describedWhat 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_survival2 of 2 parameters describedCan 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: protocol_refused (the protocol's own router refuses, the vault is dead) vs no_aggregator_quote (no same-chain swap into the underlying, common for LP vaults; redeeming by hand may still work). The probe is SAME-CHAIN only: USDC on the vault's own chain. It says nothing about bridging in from elsewhere. Route tracking covers EVM chains only: a Solana vault returns tracked:false (not tracked, neither a pass nor a failure). A vault that was never screened returns screened:false with no verdict — never a fabricated one. Call this BEFORE moving money. Read-only.
list_open_alerts2 of 2 parameters describedOpen 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_score2 of 2 parameters describedWhy 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, not a recomputation. Returns found:false when unscored. Read-only.
compare_vaults1 of 1 parameter describedSide-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, vaults flagged notYieldProduct ranked after the others (each entry also has notYieldProduct: true when the vault earns about nothing; null when the API does not report it). Unscored vaults come back found:false rather than silently dropped. Read-only.
Tested by ConnectATD. Spotted a mistake? Tell us.