AtlasYield MCP server
club.atlasyield/mcpatlasyield.clubstreamable-httpv0.5.0Scanned
DeFi vault judgment for agents: 16-factor Atlas Score, route survival, blowup alerts. Read-only.
7 tools: 3 change things and 4 only read.
- Reads private data · 4
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AtlasYield MCP server can do
The AtlasYield MCP server is published by atlasyield.club, a domain the MCP Registry verified. It has 7 tools. It can create or change data (3 tools: find_vaults, check_route_survival and list_open_alerts), but cannot delete data. 4 tools only read.
4 tools read private data (find_vaults, get_vault_score, get_coverage and 1 more).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 0.5.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 3Claude Code: ask
check_route_survivalCan a deposit into this vault be exited at size, measured today?No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
find_vaultsStart here when you do not already have a vault address.Reads private data1 finding
Why it is in this group
- The name "find_vaults" says "find": a word for reading.
- The description's first verb is "start": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- private-dataThe name "find_vaults" says "find" and "vault": it reads secrets.
- private-dataThe description's first sentence says "vault": it reads secrets.
Findings
- Warn
The server marks "find_vaults" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "find_vaults" says "find": a word for reading.
Description, as the server wrote it 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, no_yield, ...), 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_open_alertsOpen blowup-monitor alerts from the published daily snapshot: score-band exits, fast composite breaks, yield collapse, TVL flight, exploit flags, delistings.1 finding
Why it is in this group
- The name "list_open_alerts" says "list": a word for reading.
- The description's first verb is "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "list_open_alerts" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "list_open_alerts" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
compare_vaultsSide-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, vaults flagged notYi…Reads private dataNo findings
Why it is in this group
- The name "compare_vaults" says "compare": a word for reading.
What it can reach
- private-dataThe name "compare_vaults" says "compare" and "vault": it reads secrets.
- private-dataThe description's first sentence says "vault": it reads secrets.
Description, as the server wrote it 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, vaults flagged notYieldProduct ranked after the others (each entry also has notYieldProduct: true when the vault earns about nothing; null when the API does not report it). Unscored vaults come back found:false rather than silently dropped. Read-only.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
explain_vault_scoreWhy 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 …No findings
Why it is in this group
- The name "explain_vault_score" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_coverageWhat the Atlas Score Index covers right now: number of scored vaults, total TVL, composite score spread, and counts by protocol and chain.Reads private dataNo findings
Why it is in this group
- The name "get_coverage" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "vault": it reads secrets.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_vault_scoreLatest 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.Reads private dataNo findings
Why it is in this group
- The name "get_vault_score" says "get": a word for reading.
What it can reach
- private-dataThe name "get_vault_score" says "get" and "vault": it reads secrets.
- private-dataThe description's first sentence says "vault": it reads secrets.
Description, as the server wrote it 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. Each vault also carries holdingsScore: the score from what it holds, with its cap; published:false means it is not yet the headline composite. notYieldProduct: true means it earns essentially nothing; do not present the score as a reason to deposit for yield. Returns found:false when the vault is not in the scored universe. Read-only.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://atlasyield.club/mcp: tools/list returned 7 tools to an anonymous client, including find_vaults (write), check_route_survival (write), list_open_alerts (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnfind_vaults
The server marks "find_vaults" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "find_vaults" says "find": a word for reading.
- Warnlist_open_alerts
The server marks "list_open_alerts" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "list_open_alerts" says "list": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:compare_vaultsOnly readsdescription
- Changed:find_vaultsChanges thingsdescription
- Changed:get_vault_scoreOnly readsdescription
Install
Pinned to version 0.5.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http atlasyield https://atlasyield.club/mcpclaude mcp add --transport http atlasyield https://atlasyield.club/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__atlasyield__get_vault_score",
"mcp__atlasyield__get_coverage",
"mcp__atlasyield__explain_vault_score",
"mcp__atlasyield__compare_vaults"
],
"ask": [
"mcp__atlasyield__find_vaults",
"mcp__atlasyield__check_route_survival",
"mcp__atlasyield__list_open_alerts"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as atlasyield. Review it before you use it.
Capability tags behind 4 rules
- mcp__atlasyield__find_vaults private-data
- mcp__atlasyield__get_vault_score private-data
- mcp__atlasyield__get_coverage private-data
- mcp__atlasyield__compare_vaults private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/club.atlasyield/mcp/verify?hash=4c562652ae38318cde2309b7ea0cf903ab9e05139d1a41caae62a948a4592233" | jq -e '.changed == false'Pinned hash 4c562652ae38, from Nov 19, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/club.atlasyield/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/club.atlasyield/mcp)Source: MCP Registry · repository. Synced Nov 19, 2026, 06:17 UTC.
AtlasYield MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AtlasYield MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AtlasYield MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AtlasYield MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the AtlasYield MCP server have?
- 7 tools: 3 write, 4 read. find_vaults, check_route_survival, list_open_alerts, get_vault_score, get_coverage, explain_vault_score and compare_vaults.
Does the AtlasYield MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AtlasYield MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AtlasYield MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.