AtlasYield

club.atlasyieldPublished by atlasyield.clubOfficial publisherv0.4.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Read-only MCP server giving assistants AtlasYield's 16-factor DeFi vault scores, route-survival checks and blowup alerts.

What you can do
Find and rank vaults for an asset and chain, with live APY/TVL and risk flags, limited to routable vaults by default. Retrieve a single vault's latest Atlas Score, its four pillar scores and data quality. Explain a score factor by factor, including weights, raw inputs and the three weakest factors. Compare 2 to 8 vaults side by side, ranked by composite score. Check whether a deposit can be exited at size today, with a blocking verdict when no safe route exists. List open blowup-monitor alerts and report what the scored universe currently covers.
When to use it
Useful when an assistant is asked to research or compare DeFi vaults, judge whether a vault is safe to enter, or check exit liquidity before a deposit. Also suited to questions about what AtlasYield scores and which alerts are open.
Requirements
Runs as a remote endpoint or as a local process via npx (Node.js required). No API key, account or authentication is declared. Network access to the AtlasYield public API and the published score-history data is needed; the API and snapshot base URLs can be overridden with ATLAS_API_BASE and ATLAS_SNAPSHOT_BASE.
Before you install
Read-only: no deposit, signing or sending tools exist, and the README says none will be added. Scores are research and information, not investment advice, and a vault ranking is not a recommendation. Data is scored every 4 hours and alerts come from a daily snapshot, so results can lag. Queries about specific vaults are sent to the AtlasYield API.

Installation

In SourceWeft

  1. Open AtlasYield in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/club.atlasyield%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

@atlasyield/mcp

[Listed on mcpservers.org]

Read-only MCP server for the AtlasYield judgment layer. Seven tools, no key, no custody, no execution: an agent asks for judgment and is told when a route is unsafe.

ToolAnswers
find_vaultsNo vault address yet? A short ranked list for an asset and chain (chain: "base"), routable vaults only, about 2 KB. A ranking, not a recommendation.
get_vault_scoreLatest 16-factor Atlas Score for one vault (composite, label, 4 pillars, live APY/TVL).
get_coverageWhat is scored right now: vault count, TVL, score spread, by protocol and chain.
check_route_survivalCan a deposit be exited at size, measured today? blocking:true means refuse.
list_open_alertsOpen blowup-monitor alerts from the published daily snapshot.
explain_vault_scoreWhy: all 16 factors by pillar (sub-score, weight, raw input, label) and the three weakest.
compare_vaults2-8 vaults side by side, ranked by composite; unscored ones stay visible as found:false.

Data comes from the public API https://api.atlasyield.club/v1 and the published score history https://github.com/gveshk/atlasyield-score-history. Scored every 4 hours, snapshot published daily. Research and information, not investment advice.

Install

Claude Code:

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

Claude Desktop / Cursor / any stdio client (mcp.json or claude_desktop_config.json):

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

From a checkout: npm install && npm run build then use "command": "node", "args": ["<checkout>/dist/index.js"].

Docker: docker build -t atlasyield-mcp . then "command": "docker", "args": ["run", "-i", "--rm", "atlasyield-mcp"].

Try it

Is Morpho WETH on Base (0x09832347586e238841f49149c84d121bc2191c53) safe to enter at $10k?

The agent calls get_vault_score, then check_route_survival. A NO_ROUTE verdict comes back as blocking: true and a plain-English refusal.

Without an MCP client: npm run build && node scripts/smoke.mjs check_route_survival '{"chainId":8453,"address":"0x..."}' speaks raw JSON-RPC to the binary over stdio.

Environment

  • ATLAS_API_BASE — override the API base (default https://api.atlasyield.club/v1)
  • ATLAS_SNAPSHOT_BASE — override the score-history raw base

What this is not

No deposit, sign, or send tool exists here and none will be added. Execution, if offered, is a separate API with its own guards (recipient-safety, assertRouteValue) — never an MCP tool.

Docs: https://docs.atlasyield.club/api-reference/mcp · Licence: MIT · Data licence: https://atlasyield.club/data-license

Source: README.md at commit b54ccf3

Tools

7

find_vaults

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, risk flags (thin_tvl, apy_outlier, ...), 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.

ParametersassetchainlimitminApysortByminScoreminTvlUsdprotocolId

get_vault_score

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.

ParametersaddressrequiredchainIdrequired

get_coverage

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.

ParameterschainIdprotocolId

check_route_survival

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

ParametersaddressrequiredchainIdrequired

list_open_alerts

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.

ParameterschainIdminSeverity

explain_vault_score

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.

ParametersaddressrequiredchainIdrequired

compare_vaults

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.

Parametersvaultsrequired

Version history

4
  1. v0.4.0LatestOct 11, 2026
  2. v0.3.1Oct 8, 2026
  3. v0.2.4Sep 22, 2026
  4. v0.2.3Sep 22, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts