Sato Hub
Data Tool

Everstake

Official MCP server from certified staking provider Everstake exposing live APY, uptime, and staking-calculator data.

  • Sato Score49
  • ChainsMultichain
ActiveUnverifiedRecent · 2mo ago

Everstake is a partly open-source data tool, with last code activity on 2026-08-25 (Recent). Latest release on 2026-07-01. Sato Score 49/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →

See how to install Everstake →

Last commit Aug 25, 2026 · Last release Jul 1, 2026 · ★ 1

Listed from everstake.com on 2026-07-19. Install: failed on 2026-09-14. Evidence →

Website ↗GitHub ↗

Next step

Watch Everstake

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on everstake/mcp before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Everstake is a SOC 2 Type II / ISO 27001-certified institutional non-custodial staking provider supporting 130+ networks and integrating with custodians like Fireblocks, BitGo, and Anchorage. Its official MCP server (Go, self-hosted or Docker) gives agents company/product info plus live tools — uptime metrics, supported chains, and a staking calculator — and an integration-request submission tool.

Sato Score

49/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
25/35
Code transparency
13/20
Interface verifiability
0/10
Docs & demo
0/10
Listing transparency & provenance
8/15
Independent verification
3/10
View verification & embed badge →History →How the Sato Score works

Evidence — listed vs checked · what the words mean

Listed from everstake.com on 2026-07-19. Install: failed on 2026-09-14.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reportedeverstake.comas of 2026-10-21
Verification statusUnverified — not independently reviewedself-reportedeverstake.comas of 2026-10-21
Recent activitylast release 2026-07-01 · last commit 2026-08-25observedgithub.com/everstake/mcp2026-10-21
Install worksdid not complete at the install stepa measurement of the documented path, often a stale README — not a judgement of the softwareobservedgithub.com/everstake/mcp2026-09-14
Website answersanswered (HTTP 200)observedeverstake.com2026-10-21
Daily check record90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-20
Deploys asDocker, stdio, localconfidence 0.80self-reportedgithub.com/everstake/mcpas of 2026-07-26
Sato Score49/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-21

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — we ran this on Sep 14, 2026 and the install step did not complete — the commands below are the project's own, and they may simply have moved on

Runtime: Go 1.26.1+ (or Docker)

install: install failed: 1: Pulling from library/golang | go: go.mod file not found in current directory or any parent directory; see 'go help modules'
ran: mkdir -p /app || exit 1; cd /app || exit 1; export DASHBOARD_URL=https://dashboard-api.everstake.one && go run ./cmd/mcp_server

entry: skipped (install failed)
ran: d="$(ls -d /app/*/ 2>/dev/null | head -1)"; { [ -n "$d" ] && cd "$d"; } || cd /app || exit 1; go build ./...

export DASHBOARD_URL=https://dashboard-api.everstake.one
go run ./cmd/mcp_server
go run ./cmd/mcp_server — Docker alt: docker run -e DASHBOARD_URL=https://dashboard-api.everstake.one -p 8080:8080 everstake-mcp

You supply: DASHBOARD_URL (required, dashboard API base URL), MCP_TRANSPORT (optional, http|stdio, default http), PORT (optional, HTTP mode only, default 8080)

MCP invocation: go run ./cmd/mcp_server (stdio or Streamable HTTP via MCP_TRANSPORT, default HTTP on :8080, health check GET /health)

Read from the project’s own docs as of 2026-09-14. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-23

100%of 91 checks since 2026-07-23 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-21, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
49
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Multichain
Agent types
MCP server
Open source
Partial
Deploys as
Docker, stdio, local
Last checked
2026-10-21

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#staking#mcp#apy-data#institutional#non-custodial

Where Everstake fits

TradingWalletsData

Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?

See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Everstake's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Sep 26, 2026
    Edited: website url
  2. Sep 14, 2026
    Verified: deploy spec
  3. Jul 26, 2026
    Auto-enriched: deployment options
  4. Jul 24, 2026
    Sato Hub began tracking this listing
  5. Jul 19, 2026
    Listed on Sato Hub

Compared with

Alternatives to Everstake →

Related Resources

Coinbase AgentKit

Active
Framework

Coinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.

BaseEthereumMultichain
Active★ 1.3k

Hyperliquid

Active
VenueVerified

Onchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.

MultichainHyperliquid
Recent★ 506▸ Jun 2023

Model Context Protocol (MCP)

Active
Standard

Anthropic's open standard for connecting AI systems to external tools and data sources.

Unknown
Active★ 9.5k

Reference

QuestionsShowHide

Questions people ask about Everstake

Is Everstake open source?
Partly. Some of Everstake is published as source (https://github.com/everstake/mcp) and some is not. Checked as of 2026-10-21.
Which chains does Everstake support?
Everstake lists support for Multichain as of 2026-10-21.
Is Everstake still maintained?
The most recent code activity Sato Hub observed was on 2026-08-25 (last commit 2026-08-25, last release 2026-07-01), which Sato Hub labels "Recent". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Everstake?
Go 1.26.1+ (or Docker). Install: export DASHBOARD_URL=https://dashboard-api.everstake.one && go run ./cmd/mcp_server. Entry: go run ./cmd/mcp_server — Docker alt: docker run -e DASHBOARD_URL=https://dashboard-api.everstake.one -p 8080:8080 everstake-mcp. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (go run ./cmd/mcp_server (stdio or Streamable HTTP via MCP_TRANSPORT, default HTTP on :8080, health check GET /health)).
Is Everstake verified on Sato Hub?
No independent verification is on record for Everstake; its verification status is "Unverified" and its Sato Score is 49 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Everstake — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/everstake-mcp

Data last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.