@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.
This server publishes no instructions, or was last inspected before Glama recorded them.
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 |
|---|---|
| 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. 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). 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. 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 6 tools
Each tool targets a distinct concern: single-vault score, index coverage, exit route survivability, open alerts, score explanation, and multi-vault comparison. There is no meaningful overlap or ambiguity between them.
Most tools follow a verb_noun pattern (get_vault_score, get_coverage, list_open_alerts, explain_vault_score, compare_vaults), with 'check_route_survival' as a minor deviation. The names remain predictable and readable.
Six tools is well-scoped for a read-only vault scoring index. Each tool earns its place, covering scores, coverage, explanation, comparison, alerts, and pre-deposit safety checks without redundancy.
The surface covers the core scoring domain well: retrieving, explaining, comparing, coverage, alerts, and route survival. A minor gap is the lack of a way to list all scored vaults or filter by chain/protocol, but counts and coverage partially compensate.