AtlasYield
club.atlasyield/mcpVersion 0.4.0DeFi vault judgment for agents: 16-factor Atlas Score, route survival, blowup alerts. Read-only.
Status
Responds189 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:42 UTC
- Latency
- 189 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://atlasyield.club/mcpResponds189 msNo sign-in
Claude Code
claude mcp add --transport http atlasyield https://atlasyield.club/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: atlasyield
Remote MCP server URL: https://atlasyield.club/mcpCursor
{
"mcpServers": {
"atlasyield": {
"url": "https://atlasyield.club/mcp"
}
}
}VS Code
code --add-mcp '{"name":"atlasyield","type":"http","url":"https://atlasyield.club/mcp"}'Streamable HTTP
npm: @atlasyield/mcp 0.4.0Package only
npm (npx)
claude mcp add atlasyield -- npx -y @atlasyield/mcp@0.4.0Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
7 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
check_route_survivalCan 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. | No | Yes | Yes | No |
compare_vaultsSide-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. | No | Yes | Yes | No |
explain_vault_scoreWhy 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. | No | Yes | Yes | No |
find_vaultsStart 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 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. | No | Yes | Yes | No |
get_coverageWhat 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. | No | Yes | Yes | No |
get_vault_scoreLatest 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. Returns found:false when the vault is not in the scored universe. Read-only. | No | Yes | Yes | No |
list_open_alertsOpen 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. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Oct 11, 2026
- Updated
- Oct 11, 2026
- Categories (suggested)
- Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared