Everstake

com.everstakePublished by everstake.comOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint exposing Everstake's non-custodial staking data, company, product and security information, plus a staking reward calculator.

What you can do
  • Look up supported blockchain networks with APY, fees, currencies and status, and estimate staking rewards for a network and amount.
  • Read Everstake company facts: profile, products, industry solutions, custody and wallet integrations, developer docs, security certifications and contact channels.
  • Check live uptime metrics for Everstake services.
  • Submit an integration or staking inquiry to Everstake's sales team.
When to use it
Useful when an assistant needs to answer questions about staking yields, supported chains, or Everstake's products, security posture and integrations, or to hand a user's integration interest to sales. Mostly a vendor information and lead-capture endpoint rather than a general staking tool.
Requirements
The hosted endpoint is a remote Streamable HTTP service with no declared authentication, environment variables or headers. Self-hosting the open-source Go server requires Go 1.26.1+ and the DASHBOARD_URL environment variable, with optional MCP_TRANSPORT, PORT and GIN_MODE.
Before you install
The request_integration tool writes data: it submits the user's contact and inquiry details to Everstake's sales team through Pipedrive CRM, so confirm before calling it. Static responses are vendor-authored marketing content, and APY figures are estimates updated daily, not guarantees.

Installation

In SourceWeft

  1. Open Everstake in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.everstake%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "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/.

Source: README.md at commit 68f5f5f

Tools

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.

Takes no parameters.

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.

Takes no parameters.

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.

Takes no parameters.

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.

Takes no parameters.

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.

Takes no parameters.

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.

Takes no parameters.

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.

Takes no parameters.

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.

Takes no parameters.

get_uptime_metrics

Provides uptime metrics for Everstake services.

Takes no parameters.

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

Parametersjob_titlelast_namerequiredagree_newsfirst_namerequiredwork_emailrequiredlead_sourcecompany_namecompany_sitecompany_typeprimary_regioncustody_solutionproduct_of_interest+2 more

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.

Parametersamountrequirednetworkrequiredcurrencyrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts