@atlasyield/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATLAS_API_BASE | No | Override the API base | https://api.atlasyield.club/v1 |
| ATLAS_SNAPSHOT_BASE | No | Override the score-history raw base |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
AtlasYield is an independent judgment layer for on-chain yield. Scores are research, not investment advice. Call check_route_survival before any deposit; blocking:true means refuse.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_vaultsA | 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, 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_scoreA | 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. 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_coverageA | 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_survivalA | 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: 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_alertsA | 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_scoreA | 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, not a recomputation. Returns found:false when unscored. Read-only. |
| compare_vaultsA | 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, 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool maps to a distinct step in the vault workflow: universe coverage, discovery, single-vault score, factor explanation, multi-vault comparison, route screening, and alerts. The only mild overlap is among get_vault_score, explain_vault_score, and compare_vaults, which all surface the composite and pillars at different granularities, but the descriptions spell out the differences (headline score vs. 16-factor breakdown vs. 2-8 vault ranking) well enough to guide selection.
All seven names use snake_case with a clear verb_noun structure (get_coverage, find_vaults, get_vault_score, check_route_survival, list_open_alerts, explain_vault_score, compare_vaults). Verbs are used accurately and consistently, with no style mixing or ambiguous bare nouns.
Seven tools is well-scoped for a read-only vault analytics surface, with each tool earning its place as a distinct query type. Nothing feels redundant or padded, and no obvious capability is crammed into a catch-all tool.
The surface covers the full read-only lifecycle: discover the universe, find candidate vaults, score a vault, explain the score, compare vaults, screen exit routes, and check alerts. Gaps are minor — there is no historical score/trend tool beyond the before/after deltas in alerts, and no direct lookup of a vault you already know the address of without going through find_vaults or get_vault_score.