# AtlasYield (npm · @atlasyield/mcp)

DeFi vault judgment for agents: 16-factor Atlas Score, route survival, blowup alerts. Read-only.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `@atlasyield/mcp`: 72/100 (this document), [markdown](https://verifymcp.io/servers/club-atlasyield-mcp/atlasyield-mcp.md), [page](https://verifymcp.io/servers/club-atlasyield-mcp/atlasyield-mcp)

## Channel facts

- Registry: `npm`
- Package: `@atlasyield/mcp`
- Version: `0.2.4`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add club-atlasyield-mcp -- npx -y @atlasyield/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "club-atlasyield-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@atlasyield/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "club-atlasyield-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@atlasyield/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add club-atlasyield-mcp -- npx -y @atlasyield/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "club-atlasyield-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@atlasyield/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add club-atlasyield-mcp --command npx --arg -y --arg @atlasyield/mcp
```

### Hermes

```yaml
mcp_servers:
  club-atlasyield-mcp:
    command: "npx"
    args: ["-y", "@atlasyield/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "club-atlasyield-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@atlasyield/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add club-atlasyield-mcp -t stdio -c npx -a -y @atlasyield/mcp
```

### Other

```json
{
  "mcpServers": {
    "club-atlasyield-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@atlasyield/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 72, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 72, +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.

### 2026-09-23 (score 71, +33)

- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.07
- [functional improvement] MCP protocol: unverified → pass

### 2026-09-22 (score 38, −32)

- [security regression] 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.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.3 → 0.2.4

### 2026-09-21 (score 70)

First indexed and scored.

## MCP tools (6)

### `get_vault_score` (~120 tokens)

Get vault score

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.

Input parameters:

- `address` (string, required): Vault contract address (0x…); case-insensitive
- `chainId` (integer, required): EVM chain id, e.g. 1 (Ethereum), 8453 (Base), 42161 (Arbitrum)

### `get_coverage` (~117 tokens)

Get coverage

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.

Input parameters:

- `chainId` (integer): Restrict to one chain id
- `protocolId` (string): Restrict to one protocol id, e.g. morpho, aave-v3, pendle, beefy, yearn-v3, euler

### `check_route_survival` (~208 tokens)

Check route survival

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.

Input parameters:

- `address` (string, required): Vault contract address (0x…)
- `chainId` (integer, required): EVM chain id of the vault

### `list_open_alerts` (~102 tokens)

List open alerts

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.

Input parameters:

- `chainId` (integer): Restrict to one chain id
- `minSeverity` (integer): Only alerts at or above this severity (1 = lowest)

### `explain_vault_score` (~142 tokens)

Explain vault score

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.

Input parameters:

- `address` (string, required): Vault contract address (0x…); case-insensitive
- `chainId` (integer, required): EVM chain id, e.g. 1 (Ethereum), 8453 (Base), 42161 (Arbitrum)

### `compare_vaults` (~90 tokens)

Compare vaults

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.

Input parameters:

- `vaults` (array, required): 2-8 vaults to compare, any mix of chains

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/club-atlasyield-mcp/atlasyield-mcp#diagnostics

## Score history

- 2026-09-25: 72
- 2026-09-24: 72
- 2026-09-23: 71
- 2026-09-22: 38
- 2026-09-21: 70

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@atlasyield/mcp
- Socket report: https://socket.dev/npm/package/@atlasyield/mcp
- Repository: https://github.com/gveshk/atlasyield-mcp
- Website: https://docs.atlasyield.club/api-reference/mcp
- Changelog RSS feed: https://verifymcp.io/servers/club-atlasyield-mcp/atlasyield-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/club-atlasyield-mcp/atlasyield-mcp.json
- HTML version of this page: https://verifymcp.io/servers/club-atlasyield-mcp/atlasyield-mcp