Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.everstake.comRun this in your terminal
claude mcp add --transport http everstake https://mcp.everstake.comPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"everstake": {
"url": "https://mcp.everstake.com"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"everstake": {
"type": "http",
"url": "https://mcp.everstake.com"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.everstake.comMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain everstake.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Detailing Manager
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
| 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 |
DASHBOARD_URL set (required)export DASHBOARD_URL=https://your-dashboard-api-host
go run ./cmd/mcp_server
The server starts on port 8080 by default. Override with PORT= .
export DASHBOARD_URL=https://your-dashboard-api-host
export MCP_TRANSPORT=stdio go 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.
HTTP mode:
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):
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).
| 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) |
GET /health
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).
Start the container:
docker run --rm -p 8080:8080 \
-e DASHBOARD_URL=https://your-dashboard-api-host \ -e DASHBOARD_API_KEY= \ everstake-mcp
Open Inspector:
npx @modelcontextprotocol/inspector
In the UI:
Streamable HTTPhttp://localhost:8080/Container stays running across Inspector sessions.
Let Inspector launch the container so it owns stdin/stdout:
npx @modelcontextprotocol/inspector \
docker run --rm -i \ --env-file .env \ everstake-mcp
Or fill the UI manually:
STDIOdockerrun --rm -i --env-file .env everstake-mcpEach Inspector session forks a fresh container; quitting Inspector kills it.
The project uses golangci-lint with a strict configuration in .golangci.yml.
Install golangci-lint:
go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest
Run:
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.
Edit tools.yaml. Each map key is the tool name; the static_response field is returned verbatim to the AI agent.
tools:
get_company_profile: description: | ... static_response: | COMPANY: Everstake ...
To add a new static tool:
tools: in tools.yaml with static_response.ToolsConfig in internal/config/mcp_config.go with a matching yaml struct tag — the name is injected automatically via reflection.internal/server/mcp/server.go using staticTextTool().Cross-cutting rules that apply to all tool responses are in .vscode/tools_src/RULES.md. These cover:
request_integrationget_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/.