accueil / serveurs / Cloud & Infra / club.atlasyield/mcp
club.atlasyield/mcp
serveur MCP (Model Context Protocol) · atlasyield 0.3.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que club.atlasyield/mcp est sûr ?
Au dernier audit MCP Hub, le serveur MCP « club.atlasyield/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 7 outils
- check_route_survival≈ 356 tokens
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.
Paramètres, retour & exemple (2)
Paramètresaddress· string · requis
Vault contract address (0x…)chainId· integer · requis
EVM chain id of the vault
Exemple d'appel{"name": "check_route_survival", "arguments": {"address": "texte", "chainId": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - compare_vaults≈ 253 tokens
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.
Paramètres, retour & exemple (1)
Paramètresvaults· array · requis
2-8 vaults to compare, any mix of chains
Exemple d'appel{"name": "compare_vaults", "arguments": {"vaults": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - explain_vault_score≈ 245 tokens
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.
Paramètres, retour & exemple (2)
Paramètresaddress· string · requis
Vault contract address (0x…); case-insensitivechainId· integer · requis
EVM chain id, e.g. 1 (Ethereum), 8453 (Base), 42161 (Arbitrum)
Exemple d'appel{"name": "explain_vault_score", "arguments": {"address": "texte", "chainId": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - find_vaults≈ 573 tokens
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.
Paramètres, retour & exemple (8)
Paramètresasset· ? · optionnel
Underlying asset symbol, or a list of up to 10, e.g. USDC or ["USDC","USDT0"]. Exact match: USDC does not include syrupUSDC (similarAssets lists near misses)chain· ? · optionnel
Chain name (base, ethereum, arbitrum, optimism, bnb, solana) or EVM chain idlimit· integer · optionnel
Rows to return, default 5, max 10minApy· number · optionnel
Minimum live APY in percentage points, e.g. 10 for 10%sortBy· string · optionnel · composite | apy | tvl
Rank by this, descending. Default compositeminScore· number · optionnel
Minimum Atlas composite (0-100)minTvlUsd· number · optionnel
Minimum live TVL in USDprotocolId· string · optionnel
Protocol slug, e.g. morpho, aave-v3, pendle
Exemple d'appel{"name": "find_vaults", "arguments": {"asset": "texte", "chain": "texte", "limit": 1, "minApy": 1, "sortBy": "composite", "minScore": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_coverage≈ 201 tokens
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.
Paramètres, retour & exemple (2)
ParamètreschainId· integer · optionnel
Restrict to one chain idprotocolId· string · optionnel
Restrict to one protocol id, e.g. morpho, aave-v3, pendle, beefy, yearn-v3, euler
Exemple d'appel{"name": "get_coverage", "arguments": {"chainId": 1, "protocolId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_vault_score≈ 216 tokens
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.
Paramètres, retour & exemple (2)
Paramètresaddress· string · requis
Vault contract address (0x…); case-insensitivechainId· integer · requis
EVM chain id, e.g. 1 (Ethereum), 8453 (Base), 42161 (Arbitrum)
Exemple d'appel{"name": "get_vault_score", "arguments": {"address": "texte", "chainId": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_open_alerts≈ 204 tokens
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.
Paramètres, retour & exemple (2)
ParamètreschainId· integer · optionnel
Restrict to one chain idminSeverity· integer · optionnel
Only alerts at or above this severity (1 = lowest)
Exemple d'appel{"name": "list_open_alerts", "arguments": {"chainId": 1, "minSeverity": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».