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 分