AtlasYield
NPM · @ATLASYIELD/MCP · SCANNED SEP 25
DeFi vault judgment for agents: 16-factor Atlas Score, route survival, blowup alerts. Read-only.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 816 tokens (~136/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the AtlasYield MCP server?
AtlasYield runs locally as an npm package, launched with npx -y @atlasyield/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @atlasyield/mcp
claude mcp add club-atlasyield-mcp -- npx -y @atlasyield/mcp
{
"mcpServers": {
"club-atlasyield-mcp": {
"command": "npx",
"args": [
"-y",
"@atlasyield/mcp"
]
}
}
} {
"servers": {
"club-atlasyield-mcp": {
"command": "npx",
"args": [
"-y",
"@atlasyield/mcp"
]
}
}
} codex mcp add club-atlasyield-mcp -- npx -y @atlasyield/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"club-atlasyield-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@atlasyield/mcp"
],
"enabled": true
}
}
} openclaw mcp add club-atlasyield-mcp --command npx --arg -y --arg @atlasyield/mcp
mcp_servers:
club-atlasyield-mcp:
command: "npx"
args: ["-y", "@atlasyield/mcp"] {
"McpServers": {
"club-atlasyield-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@atlasyield/mcp"
]
}
}
} assistant mcp add club-atlasyield-mcp -t stdio -c npx -a -y @atlasyield/mcp
{
"mcpServers": {
"club-atlasyield-mcp": {
"command": "npx",
"args": [
"-y",
"@atlasyield/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 +33
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 22 Sept 26 −32
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.3 → 0.2.4 functional
- 21 Sept 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/@atlasyield/mcp@0.2.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_route_survival Check route survival ~208
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. A vault that was never screened returns screened:false with no verdict — never a fabricated one. Call this BEFORE moving money. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Vault contract address (0x…) |
| chainId | integer | yes | EVM chain id of the vault |
No output schema declared.
No examples provided.
compare_vaults Compare vaults ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| vaults | array | yes | 2-8 vaults to compare, any mix of chains |
No output schema declared.
No examples provided.
explain_vault_score Explain vault score ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Vault contract address (0x…); case-insensitive |
| chainId | integer | yes | EVM chain id, e.g. 1 (Ethereum), 8453 (Base), 42161 (Arbitrum) |
No output schema declared.
No examples provided.
get_coverage Get coverage ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | – | Restrict to one chain id |
| protocolId | string | – | Restrict to one protocol id, e.g. morpho, aave-v3, pendle, beefy, yearn-v3, euler |
No output schema declared.
No examples provided.
get_vault_score Get vault score ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Vault contract address (0x…); case-insensitive |
| chainId | integer | yes | EVM chain id, e.g. 1 (Ethereum), 8453 (Base), 42161 (Arbitrum) |
No output schema declared.
No examples provided.
list_open_alerts List open alerts ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | – | Restrict to one chain id |
| minSeverity | integer | – | Only alerts at or above this severity (1 = lowest) |
No output schema declared.
No examples provided.
What is the AtlasYield MCP server?
AtlasYield is an MCP server listed in the public MCP registry as club.atlasyield/mcp. DeFi vault judgment for agents: 16-factor Atlas Score, route survival, blowup alerts. Read-only. This page covers its npm package (@atlasyield/mcp).
Is the AtlasYield MCP server safe to use?
AtlasYield scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AtlasYield MCP server expose?
AtlasYield exposes 6 tools: get_vault_score, get_coverage, check_route_survival, list_open_alerts, explain_vault_score, compare_vaults. Their descriptions and schemas cost roughly 779 tokens of context every time the server is loaded.
Is the AtlasYield MCP server still maintained?
AtlasYield is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the AtlasYield MCP server under?
AtlasYield declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.