MCP.Market

AtlasYield MCP server

online · 100% uptime
by atlasyield.club·club.atlasyield/mcp·v0.4.0
No reviews yet

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

A93/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A93/100

full report

Adoption
Growing

0 stars200 downloads/wk

Reviews

Write one

Nobody has reviewed AtlasYield yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

AtlasYield tools (7)

write = sends, deletes, buys or posts
  • check_route_survivalFree

    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.

  • compare_vaultsFree

    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.

  • explain_vault_scoreFree

    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.

  • find_vaultsFree

    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.

  • get_coverageFree

    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.

  • get_vault_scoreFree

    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.

  • list_open_alertsFree

    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.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings
  • Code scan12 source files scanned25/25
  • Live reliabilityremote reachable in 666ms20/20
  • Tool poisoning7 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 24 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 93/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How AtlasYield compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
93/100
higher than 96% of 48,255 servers
Tools
7
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
265 ms
faster than 53% of 30,031 servers
Downloads a week
200
more than 75% of 12,191 servers with a package

What its tools let an agent do: 7 read

Release history: 4 versions in the registry since 2026-09-21, latest 2026-10-11, typically one every 3 days.

Install AtlasYield in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://atlasyield.club/mcp
Add to Cursor

What the publisher says

From the AtlasYield repository's README, as published. We do not edit it. Read it on GitHub

@atlasyield/mcp

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

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:

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

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

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

From a checkout: npm install && npm run build then use "command": "node", "args": ["/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 getvaultscore, then checkroutesurvival. 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 checkroutesurvival '{"chainId":8453,"address":"0x..."}' speaks raw JSON-RPC to the binary over stdio.

Environment

  • ATLASAPIBASE — override the API base (default https://api.atlasyield.club/v1)
  • ATLASSNAPSHOTBASE — 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

Nothing above is checked by us. What we check is on the safety report.

AtlasYield: common questions

Is AtlasYield MCP server safe?
Yes, by our scan: it is graded A (93/100). Read the AtlasYield safety report
How do I install AtlasYield?
It runs remotely at atlasyield.club. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does AtlasYield need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is AtlasYield maintained?
The last commit was 27 days ago (2026-10-08). The latest release is v0.4.0.
Is AtlasYield up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does AtlasYield compare with other MCP servers?
safety score 93/100 (higher than 96% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.