MCP server

@atlasyield/mcp wraps the public /v1 API and the published score history as a Model Context Protocol server over stdio.

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

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

Tool	Input	Gives you
`get_vault_score`	`chainId`, `address`	Latest composite, label, the four pillar scores, live APY/TVL, `found:false` if unscored.
`get_coverage`	`chainId?`, `protocolId?`	Vault count, TVL, composite min/median/max, counts by protocol and chain.
`check_route_survival`	`chainId`, `address`	Today’s round-trip route screen. `blocking:true` (NO_ROUTE, DANGEROUS, UNPRICEABLE) means refuse the deposit. `screened:false` means unjudged, never cleared.
`list_open_alerts`	`chainId?`, `minSeverity?`	Open monitor alerts from the daily snapshot with score before/after.

Every result carries the disclaimer: research and information, not investment advice.

What it refuses to do

There is no deposit, sign, or send tool, and none will be added. The point of the server is the refusal: an agent asks whether a route survives a round trip and is told no before it moves a user’s money. Execution, where it exists, is a separate API with its own guards, not an MCP tool. Source: apps/mcp in the AtlasYield repo. Data licence: https://atlasyield.club/data-license

Getting started

Endpoints

What it refuses to do

​What it refuses to do

What it refuses to do