AtlasYield MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Read-only AtlasYield vault scores and route-survival judgments: Do route blocking and coverage uncertainty remain explicit without suggesting custody or execution authority?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Read-only DeFi vault judgment and route-survival risk data for agents.

What we know

MCP over AtlasYield's public risk layer. It returns multi-factor vault scores, factor explanations, comparisons, route-survival verdicts, coverage and alerts. The MCP intentionally does not deposit, sign or send transactions.

Maintenance / activity evidence

@atlasyield/mcp 0.2.4 published 2026-09-22T09:51:28.541Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Official MCP is read-only and has no custody/execution tools.
Authentication not yet verified.
Sensitive access: Investment-research queries only

No execution authority; risk is relying on stale/incomplete research.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do route blocking and coverage uncertainty remain explicit without suggesting custody or execution authority?

The bounded review of the publisher's documented Read-only AtlasYield vault scores and route-survival judgments and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

No execution authority; risk is relying on stale/incomplete research.
Official MCP is read-only and has no custody/execution tools.
Queries fetch public AtlasYield score/route data.
Sensitive access: Investment-research queries only
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Read-only research is not investment advice.
Scores and route probes are time-sensitive snapshots.
The separate Atlas Engine may prepare transactions, but execution is not part of this MCP.
Coverage is limited to rated protocols/vaults.

Original activity observations

@atlasyield/mcp 0.2.4 published 2026-09-22T09:51:28.541Z

Technical identity

npm/@atlasyield/mcp

Exact implementation source: https://www.npmjs.com/package/@atlasyield/mcp ↗
Reviewed resource type: MCP Server
Repository identity: gveshk/atlasyield-mcp
Package identity: npm:@atlasyield/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@atlasyield/mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
atlasyield.club/
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
docs.atlasyield.club/api-reference/mcp
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Provider documents remote HTTP endpoint; registration is not a locally installed npm process unless explicitly choosing the alternate local route.
client registration · Claude Code only · retained baseline · Publisher instructions
claude mcp add --transport http atlasyield https://atlasyield.club/mcp
Configure / authenticate
MCP100 setup guide
Hosted MCP https://atlasyield.club/mcp (or optional local stdio `npx -y @atlasyield/mcp`); no wallet required for read-only vault analysis.
Check connection
Suggested check
Check read-only `find_vaults`; do not deposit or execute transactions.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `atlasyield`, remove the client entry with `claude mcp remove atlasyield`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove atlasyield

Official Documentation & Sources

https://www.npmjs.com/package/@atlasyield/mcp ↗

What it does

MCP over AtlasYield's public risk layer. It returns multi-factor vault scores, factor explanations, comparisons, route-survival verdicts, coverage and alerts. The MCP intentionally does not deposit, sign or send transactions.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing
Best fit: Read-only DeFi vault judgment and route-survival risk data for agents.

Representative uses

Get/explain vault score
Compare vaults
Check route survival
List risk alerts
Inspect coverage

Limitations

Read-only research is not investment advice.
Scores and route probes are time-sensitive snapshots.
The separate Atlas Engine may prepare transactions, but execution is not part of this MCP.
Coverage is limited to rated protocols/vaults.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Official MCP is read-only and has no custody/execution tools.
Data handling: Queries fetch public AtlasYield score/route data.
Cost: free_with_paid_data_tiers
Risk and cautions: No execution authority; risk is relying on stale/incomplete research.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Investment-research queries only
Risk level: low

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Get/explain vault score; Compare vaults; Check route survival; List risk alerts; Inspect coverage.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @atlasyield/mcp. Recorded transport: stdio. Recorded environment-variable notes: ATLAS_API_BASE (optional); ATLAS_SNAPSHOT_BASE (optional). No configuration values are supplied here. Prerequisites: MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No API key for public MCP/API use.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Official MCP is read-only and has no custody/execution tools.

What data-handling boundary should I consider?

Queries fetch public AtlasYield score/route data. Recorded sensitive-access context: Investment-research queries only.

What limitations and risks should I check before use?

No execution authority; risk is relying on stale/incomplete research. Read-only research is not investment advice. Scores and route probes are time-sensitive snapshots. The separate Atlas Engine may prepare transactions, but execution is not part of this MCP. Coverage is limited to rated protocols/vaults. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is free with paid data tiers. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.