AtlasYield
REMOTE · ATLASYIELD.CLUB · 2 COMPONENTS · SCANNED OCT 9
DeFi vault judgment for agents: 16-factor Atlas Score, route survival, blowup alerts. Read-only.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
remote · atlasyield.club
claude mcp add --transport http club-atlasyield-mcp 'https://atlasyield.club/mcp'
{
"mcpServers": {
"club-atlasyield-mcp": {
"url": "https://atlasyield.club/mcp"
}
}
} {
"servers": {
"club-atlasyield-mcp": {
"type": "http",
"url": "https://atlasyield.club/mcp"
}
}
} [mcp_servers.club-atlasyield-mcp] url = "https://atlasyield.club/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"club-atlasyield-mcp": {
"type": "remote",
"url": "https://atlasyield.club/mcp",
"enabled": true
}
}
} openclaw mcp add club-atlasyield-mcp --url 'https://atlasyield.club/mcp' --transport streamable-http
mcp_servers:
club-atlasyield-mcp:
url: "https://atlasyield.club/mcp" {
"McpServers": {
"club-atlasyield-mcp": {
"Transport": "http",
"Url": "https://atlasyield.club/mcp"
}
}
} assistant mcp add club-atlasyield-mcp -t streamable-http -u 'https://atlasyield.club/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 9 Oct 2026 · Probed https://atlasyield.club/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=atlasyield.club | CN=YR1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | RSA 2048 | SHA256-RSA | 647fcfb4504a30ca5a74e15089ce43352a9 |
| SANs: atlasyield.club | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of atlasyield.club. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| club. | present | 54682 | 8 | Verified |
| atlasyield.club. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://atlasyield.club/mcp | Verified | 200 | |
| http (plaintext) | http://atlasyield.club/mcp | HTTPS enforced | 308 | https://atlasyield.club/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_route_survival Check route survival ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Vault contract address (0x…) |
| chainId | integer | yes | EVM chain id of the vault |
No output schema declared.
No examples provided.
compare_vaults Compare vaults ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| vaults | array | yes | 2-8 vaults to compare, any mix of chains |
No output schema declared.
No examples provided.
explain_vault_score Explain vault score ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Vault contract address (0x…); case-insensitive |
| chainId | integer | yes | EVM chain id, e.g. 1 (Ethereum), 8453 (Base), 42161 (Arbitrum) |
No output schema declared.
No examples provided.
find_vaults Find vaults ~268
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_coverage Get coverage ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | – | Restrict to one chain id |
| protocolId | string | – | Restrict to one protocol id, e.g. morpho, aave-v3, pendle, beefy, yearn-v3, euler |
No output schema declared.
No examples provided.
get_vault_score Get vault score ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Vault contract address (0x…); case-insensitive |
| chainId | integer | yes | EVM chain id, e.g. 1 (Ethereum), 8453 (Base), 42161 (Arbitrum) |
No output schema declared.
No examples provided.
list_open_alerts List open alerts ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | – | Restrict to one chain id |
| minSeverity | integer | – | Only alerts at or above this severity (1 = lowest) |
No output schema declared.
No examples provided.
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.