MCP server

The Atlas MCP server wraps the public /v1 API and the published score history as a Model Context Protocol server. Use it hosted at a URL, or run it locally. It is listed in the official MCP registry as club.atlasyield/mcp.

Connect

Hosted: nothing to install

https://atlasyield.club/mcp

MCP Streamable HTTP, read-only, no key. In Claude Code:

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

Any client that accepts a remote MCP server URL can use the same address; the field it goes in depends on the client. To check it from a terminal:

curl -s https://atlasyield.club/mcp \
  -H "content-type: application/json" \
  -H "accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Both headers are required; without the accept header the server answers 406. Opening the URL in a browser shows a 405 message, which is expected: the endpoint only accepts POST.

Local: run it yourself

@atlasyield/mcp on npm runs the same tools over stdio.

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

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

Tools

Tool	Input	Gives you
`find_vaults`	`asset?`, `chain?` (name or id), `protocolId?`, `minScore?`, `minTvlUsd?`, `sortBy?`, `limit?` (default 5, max 10)	Start here when you have no vault address. A short ranked list of scored vaults a deposit can reach, with composite, label, live APY/TVL, `routable` and a citable page URL. Rows with no deposit route or fallback data are excluded. A ranking, not a recommendation. About 2 KB per call.
`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 same-chain round-trip route screen. `blocking:true` (NO_ROUTE, DANGEROUS, UNPRICEABLE) means refuse the deposit; `reasonClass` says why (`protocol_refused` = the vault is dead, `no_aggregator_quote` = no priced same-chain route into the underlying). `screened:false` means unjudged, never cleared. Cross-chain is not probed.
`list_open_alerts`	`chainId?`, `minSeverity?`	Open monitor alerts from the daily snapshot with score before/after.
`explain_vault_score`	`chainId`, `address`	Why the score is what it is: all 16 factors grouped by pillar with sub-score, weight, raw input and label, plus the three weakest factors.
`compare_vaults`	`vaults[]` (2-8 of `chainId`, `address`)	Side-by-side scores, pillars, live APY/TVL, yieldQuality and exitSafety, ranked by composite. Unscored entries come back `found:false`.

Every result carries the disclaimer: research and information, not investment advice. A good first call is find_vaults (for example asset: "USDC", chain: "base"). It returns a short list you can act on, and each row carries what the other tools need. Then call check_route_survival for the vault you pick, before any deposit.

About the hosted endpoint

Stateless. Each request stands alone and replies with plain JSON, not a stream. During initialize the server returns an Mcp-Session-Id header and compliant clients send it back on later requests. It only carries the client name for our usage counts and is not used for anything else.
Same data as the API. The hosted tools read the same /v1 data and share its disclaimer. Browser-based MCP clients can call it: CORS is open and the session header is exposed.
Shared infrastructure. All hosted callers share one upstream request budget. Under heavy load a call can come back as a tool error mentioning the rate limit; retry after the interval it states. For sustained or latency-sensitive use, run the server locally so requests come from your own address, or call /v1 directly.
What we log. For each hosted call: the time, your IP address, the client name and version your MCP client announces, the method, the tool name, the outcome and how long it took. We do not log tool arguments.

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: https://github.com/gveshk/atlasyield-mcp. Data licence: https://atlasyield.club/data-license

Getting started

Endpoints

Connect

Hosted: nothing to install

Local: run it yourself

Tools

About the hosted endpoint

What it refuses to do

​Connect

​Hosted: nothing to install

​Local: run it yourself

​Tools

​About the hosted endpoint

​What it refuses to do

Connect

Hosted: nothing to install

Local: run it yourself

Tools

About the hosted endpoint

What it refuses to do