# AtlasYield (remote · atlasyield.club)

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

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

## Components

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

## Channel facts

- Endpoint: `https://atlasyield.club/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-09.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1084 tokens (~154/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the AtlasYield MCP server?

AtlasYield is a hosted endpoint at https://atlasyield.club/mcp, so there is nothing to install locally. 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 --transport http club-atlasyield-mcp 'https://atlasyield.club/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "club-atlasyield-mcp": {
      "url": "https://atlasyield.club/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "club-atlasyield-mcp": {
      "type": "http",
      "url": "https://atlasyield.club/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.club-atlasyield-mcp]
url = "https://atlasyield.club/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "club-atlasyield-mcp": {
      "type": "remote",
      "url": "https://atlasyield.club/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add club-atlasyield-mcp --url 'https://atlasyield.club/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  club-atlasyield-mcp:
    url: "https://atlasyield.club/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "club-atlasyield-mcp": {
      "Transport": "http",
      "Url": "https://atlasyield.club/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add club-atlasyield-mcp -t streamable-http -u 'https://atlasyield.club/mcp'
```

### Other

```json
{
  "mcpServers": {
    "club-atlasyield-mcp": {
      "type": "http",
      "url": "https://atlasyield.club/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-09 (score 67)

First indexed and scored.

## MCP tools (7)

### `find_vaults` (~268 tokens)

Find vaults

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, whether a deposit can reach it (routable), and a citable page URL. Vaults with no deposit route and rows scored on fallback data are excluded. Ranked by Atlas composite, a ranking and not a recommendation. Take a chosen vaultId/address to check_route_survival before any deposit. Read-only.

Input parameters:

- `asset` (string): Underlying asset symbol, e.g. USDC, WETH, USDT
- `chain`: Chain name (base, ethereum, arbitrum, optimism, bnb, solana) or EVM chain id
- `limit` (integer): Rows to return, default 5, max 10
- `minScore` (number): Minimum Atlas composite (0-100)
- `minTvlUsd` (number): Minimum live TVL in USD
- `protocolId` (string): Protocol slug, e.g. morpho, aave-v3, pendle
- `sortBy` (string): Rank by this, descending. Default composite

### `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: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/club-atlasyield-mcp/atlasyield#diagnostics

## Score history

- 2026-10-09: 67

## 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 hosted endpoint (https://atlasyield.club/mcp).

### Is the AtlasYield MCP server safe to use?

AtlasYield scores 67 out of 100 on VerifyMCP. 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 7 tools: find_vaults, get_vault_score, get_coverage, check_route_survival, list_open_alerts, and 2 more. Their descriptions and schemas cost roughly 1,047 tokens of context every time the server is loaded.

### Does the AtlasYield MCP server require authentication?

No. We connected to AtlasYield without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the AtlasYield MCP server still maintained?

AtlasYield is still listed as active in the MCP registry. We last reached this channel on 9 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://atlasyield.club/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.xml
- Changelog JSON feed: https://verifymcp.io/servers/club-atlasyield-mcp/atlasyield.json
- HTML version of this page: https://verifymcp.io/servers/club-atlasyield-mcp/atlasyield