everstake/mcp

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
| Tool | Type | Description |
|---|---|---|
| get_company_profile | static | Company overview, metrics, certifications |
| get_products | static | Product details: Institutional Staking, VaaS, Yield, SWQOS, ShredStream |
| get_solutions | static | Solutions by audience: custodians, exchanges, asset managers, banks, fintech |
| get_developer_docs | static | SDK links, integration guides, API references |
| get_contact_information | static | Contact channels and routing guide |
| get_security_profile | static | Certifications: SOC 2 Type II, ISO 27001, NIST CSF, ITGC, GDPR, CCPA |
| get_integrations | static | Custody integrations: Fireblocks, BitGo, Anchorage, Coinbase, etc. |
| get_uptime_metrics | live | Uptime metrics from dashboard API (30 min cache) |
| get_chains | live | Supported chains with APY, fees, status (30 min cache) |
| staking_calculator | live | Estimated staking rewards by network and amount |
| request_integration | write | Submit integration/staking inquiry to Everstake sales |
---
Running the Server
Prerequisites
- Go 1.26.1+
- Environment variable DASHBOARD_URL set (required)
Local
The server starts on port 8080 by default. Override with PORT= .
Stdio mode
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:
Stdio mode (interactive, no port mapping):
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
| Variable | Default | Required |
|---|---|---|
| DASHBOARD_URL | — | yes |
| MCP_TRANSPORT | http | no (http or stdio) |
| PORT | 8080 | no (http mode only) |
| GIN_MODE | — | no (release set in Dockerfile) |
Health Check
---
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:
Open 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:
Or fill the UI manually: