Everstake

com.everstake由 everstake.com 發布官方發布者v1.0.0更新於 Oct 24, 2026

MCP server connecting AI agents to non-custodial staking data across 130+ networks.

已驗證Streamable HTTP可網頁執行金融商業與電商

概覽

AI 產生的概覽

遠端 MCP 端點，提供 Everstake 的非託管質押資料、公司、產品與安全資訊，以及質押報酬估算。

可以做什麼
  • 查詢支援的區塊鏈網路及其 APY、費用、幣種與狀態，並依網路和金額估算質押報酬。
  • 讀取 Everstake 公司資料：概況、產品、產業解決方案、託管與錢包整合、開發者文件、安全認證與聯絡方式。
  • 查看 Everstake 服務的即時上線率指標。
  • 代使用者向 Everstake 業務團隊提交整合或質押洽詢。
適用情境
適合需要回答質押報酬、支援鏈、Everstake 產品、安全資質與整合情況等問題的情境，或把使用者的整合意願轉交業務。它更像廠商資訊與名單收集端點，而非通用質押工具。
執行需求
託管端點是遠端 Streamable HTTP 服務，未宣告驗證、環境變數或請求標頭。自行部署開源 Go 服務需要 Go 1.26.1+ 及 DASHBOARD_URL 環境變數，可選 MCP_TRANSPORT、PORT 和 GIN_MODE。
安裝前請注意
request_integration 工具會寫入資料：透過 Pipedrive CRM 把使用者的聯絡方式和洽詢內容提交給 Everstake 業務團隊，呼叫前應先取得使用者同意。靜態回覆為廠商撰寫的行銷內容，APY 為每日更新的估算值，並非保證報酬。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Everstake，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.everstake%2Fmcp/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "everstake": {
      "type": "http",
      "url": "https://mcp.everstake.com/"
    }
  }
}

README

Everstake MCP Server

MCP server exposing Everstake staking data and company information to AI agents. Built in Go using modelcontextprotocol/go-sdk.

Transports: Streamable HTTP (MCP 2025-03-26 spec, single / endpoint) or stdio. Selected via MCP_TRANSPORT.

Available Tools

ToolTypeDescription
get_company_profilestaticCompany overview, metrics, certifications
get_productsstaticProduct details: Institutional Staking, VaaS, Yield, SWQOS, ShredStream
get_solutionsstaticSolutions by audience: custodians, exchanges, asset managers, banks, fintech
get_developer_docsstaticSDK links, integration guides, API references
get_contact_informationstaticContact channels and routing guide
get_security_profilestaticCertifications: SOC 2 Type II, ISO 27001, NIST CSF, ITGC, GDPR, CCPA
get_integrationsstaticCustody integrations: Fireblocks, BitGo, Anchorage, Coinbase, etc.
get_uptime_metricsliveUptime metrics from dashboard API (30 min cache)
get_chainsliveSupported chains with APY, fees, status (30 min cache)
staking_calculatorliveEstimated staking rewards by network and amount
request_integrationwriteSubmit integration/staking inquiry to Everstake sales

Running the Server

Prerequisites

  • Go 1.26.1+
  • Environment variable DASHBOARD_URL set (required)

Local

bash
export DASHBOARD_URL=https://your-dashboard-api-hostgo run ./cmd/mcp_server

The server starts on port 8080 by default. Override with PORT=<port>.

Stdio mode

bash
export DASHBOARD_URL=https://your-dashboard-api-hostexport MCP_TRANSPORT=stdiogo run ./cmd/mcp_server

In stdio mode, the HTTP server, /health endpoint, and rate limiting are disabled. Logs go to stderr; stdout carries the MCP JSON-RPC protocol.

Docker

HTTP mode:

bash
docker build -t everstake-mcp .docker run -e DASHBOARD_URL=https://your-dashboard-api-host -p 8080:8080 everstake-mcp

Stdio mode (interactive, no port mapping):

bash
docker run --rm -i \  -e DASHBOARD_URL=https://your-dashboard-api-host \  -e MCP_TRANSPORT=stdio \  everstake-mcp

Use -i to keep stdin attached for the JSON-RPC protocol; do not pass -t (a TTY breaks line-based JSON framing). For MCP clients that launch the server as a subprocess, point command at docker with args matching the above, or wrap in a helper script (see .vscode/stdio_docker.sh for an example using --env-file).

Environment Variables

VariableDefaultRequired
DASHBOARD_URL—yes
MCP_TRANSPORThttpno (http or stdio)
PORT8080no (http mode only)
GIN_MODE—no (release set in Dockerfile)

Health Check

GET /health

Debugging with MCP Inspector

MCP Inspector is the official tool for poking at MCP servers — list tools, call them, see raw JSON-RPC.

Stdio note: stdio servers are owned by the parent process; you cannot connect Inspector to an already-running stdio container. Inspector must launch the subprocess itself. For an interactive session you can reconnect to, use HTTP mode (option below).

HTTP mode (recommended for general debugging)

Start the container:

bash
docker run --rm -p 8080:8080 \  -e DASHBOARD_URL=https://your-dashboard-api-host \  -e DASHBOARD_API_KEY=<key> \  everstake-mcp

Open Inspector:

bash
npx @modelcontextprotocol/inspector

In the UI:

  • Transport Type: Streamable HTTP
  • URL: http://localhost:8080/

Container stays running across Inspector sessions.

Stdio mode (verify stdio transport)

Let Inspector launch the container so it owns stdin/stdout:

bash
npx @modelcontextprotocol/inspector \  docker run --rm -i \    --env-file .env \    everstake-mcp

Or fill the UI manually:

  • Transport Type: STDIO
  • Command: docker
  • Arguments: run --rm -i --env-file .env everstake-mcp

Each Inspector session forks a fresh container; quitting Inspector kills it.

Linting

The project uses golangci-lint with a strict configuration in .golangci.yml.

Install golangci-lint:

bash
go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest

Run:

bash
make lint

Key rules enforced: staticcheck (all checks), gosec, gocritic (diagnostic/style/performance tags), revive (40+ rules including early-return, error-strings, var-naming), errchkjson, bodyclose, contextcheck, and more. nolintlint requires specific lint directives — bare //nolint is not allowed.

Editing Tool Responses

Static tools

Edit tools.yaml. Each map key is the tool name; the static_response field is returned verbatim to the AI agent.

yaml
tools:  get_company_profile:    description: |      ...    static_response: |      COMPANY: Everstake      ...

To add a new static tool:

  1. Add an entry under tools: in tools.yaml with static_response.
  2. Add a corresponding field to ToolsConfig in internal/config/mcp_config.go with a matching yaml struct tag — the name is injected automatically via reflection.
  3. Register it in internal/server/mcp/server.go using staticTextTool().

Content rules

Cross-cutting rules that apply to all tool responses are in .vscode/tools_src/RULES.md. These cover:

  • Certification differentiator language
  • Non-custodial positioning
  • Vault product disclaimers
  • APY disclaimer wording
  • Lead source tagging for request_integration

Dynamic tools

get_uptime_metrics and get_chains fetch live data from the dashboard API with a 30-minute in-memory cache. Their handlers are in internal/server/mcp/dashboard.go. The underlying API client lives in pkg/everstake/dashboard/.

來源：README.md，提交 68f5f5f

工具

11

get_chains

Provides an up to date list of supported blockchain networks by Everstake and info about these chains: fees, aprs, supported currencies, active/inactive statuses, etc.

無需輸入參數。

get_company_profile

Complete company information for Everstake: overview, metrics, certifications, products, clients, and contact details. Use when users need comprehensive facts about Everstake as a company.

無需輸入參數。

get_contact_information

Comprehensive contact information and routing guide for Everstake inquiries, including social media, company resources, and purpose-specific contact channels. Use when users need to contact Everstake or find specific company resources.

無需輸入參數。

get_developer_docs

Comprehensive developer resources and integration documentation for Everstake's staking and yield infrastructure. Use this tool when developers need SDK documentation, integration guides, API references, or technical implementation details.

無需輸入參數。

get_integrations

Comprehensive integration information for Everstake: custody platform integrations, wallet partnerships, and developer SDKs. Use when users need details about integrating Everstake with existing platforms, custody solutions, or development frameworks.

無需輸入參數。

get_products

Detailed information about Everstake's product offerings: features, use cases, pricing, and technical specifications. Use when users need specific product details for decision-making or integration planning.

無需輸入參數。

get_security_profile

Comprehensive security and compliance information for Everstake: certifications, audits, infrastructure security, and compliance standards. Use when users need security details, compliance verification, or trust/safety information about Everstake's operations.

無需輸入參數。

get_solutions

Industry-specific solutions and integration approaches for different client segments: custodians, exchanges, asset managers, banks, and fintech. Use when users need tailored solution guidance for their specific business type or integration scenario.

無需輸入參數。

get_uptime_metrics

Provides uptime metrics for Everstake services.

無需輸入參數。

request_integration

Submit an integration or staking inquiry on behalf of a user. All submissions are routed to Everstake's sales team via Pipedrive CRM. Use when a user expresses intent to integrate with Everstake, explore staking services, or request more information about products. Collect required fields (first_name, last_name, work_email) conversationally and gather optional fields where available. The lead_source field is set automatically by the server — do not ask the user for it. IF Submission fails, you can try contacting Everstake via form at https://everstake.com/contact-us

輸入參數job_titlelast_name必填agree_newsfirst_name必填work_email必填lead_sourcecompany_namecompany_sitecompany_typeprimary_regioncustody_solutionproduct_of_interest另有 2 個

staking_calculator

Interactive staking reward estimator. Provide a network and stake amount to receive estimated annual and monthly rewards based on current APY. Works only with networks provided by the get_chains tool. Data freshness: APY rates updated daily. MUST HAVE either currency or chain set.

輸入參數amount必填network必填currency必填

版本歷史

1
  1. v1.0.0最新Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分