one.everstake/mcp
REMOTE · MCP.EVERSTAKE.ONE · SCANNED AUG 3
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 929 tokens (~84/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.everstake.one
claude mcp add --transport http one-everstake-mcp https://mcp.everstake.one/
[mcp_servers.one-everstake-mcp] url = "https://mcp.everstake.one/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"one-everstake-mcp": {
"type": "remote",
"url": "https://mcp.everstake.one/",
"enabled": true
}
}
} openclaw mcp add one-everstake-mcp --url https://mcp.everstake.one/ --transport streamable-http
mcp_servers:
one-everstake-mcp:
url: "https://mcp.everstake.one/" {
"mcpServers": {
"one-everstake-mcp": {
"type": "http",
"url": "https://mcp.everstake.one/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.everstake.one
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=everstake.one | CN=WE1,O=Google Trust Services,C=US | 14 Jun 2026 | 12 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 2775b3a4b87fbc3013c62dee1ad9c937 |
| SANs: everstake.one, *.everstake.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC secure
Validation of mcp.everstake.one. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| everstake.one. | present | 2371 | 13 | Verified |
| mcp.everstake.one. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.everstake.one | Verified | 200 | |
| http (plaintext) | http://mcp.everstake.one | HTTPS enforced | 301 | https://mcp.everstake.one/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_chains ~44
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_company_profile ~43
Complete company information for Everstake: overview, metrics, certifications, products, clients, and contact details. Use when users need comprehensive facts about Everstake as a company.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_contact_information ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_developer_docs ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_integrations ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_products ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_security_profile ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_solutions ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_uptime_metrics ~18
Provides uptime metrics for Everstake services.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_integration ~421
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.one/contact-us
| Name | Type | Req | Description |
|---|---|---|---|
| agree_news | boolean | — | Whether the contact consents to receive Everstake marketing communications |
| approximate_stake_size | string | — | Approximate stake size: <$1M, $2M–$5M, $5M–$10M, >$10M |
| company_name | string | — | Name of the company |
| company_site | string | — | Company website URL (optional, can be inferred from email domain) |
| company_type | string | — | Type of company |
| custody_solution | string | — | Custody solution: Anchorage, BitGo, Circle, Coinbase Custody, Copper, Fireblocks, Gemini, Ledger Enterprise, MetaMask, Sygnum, Taurus Group, Self Custody, Other |
| first_name | string | yes | First name of the contact |
| implementation_timeline | string | — | Implementation timeline: ASAP, 1–3 Months, 3+ Months |
| job_title | string | — | Job title of the contact |
| last_name | string | yes | Last name of the contact |
| lead_source | string | — | Source of the lead — set automatically by the server, do not ask the user |
| primary_region | string | — | Primary region of the company: North America, Europe, LATAM, APAC, MENA |
| product_of_interest | string | — | Product of interest: Staking, Vaults, Data & Analytics |
| work_email | string | yes | Work email address of the contact |
No output schema declared.
No examples provided.
staking_calculator ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | The amount of cryptocurrency to stake. |
| currency | string | yes | The ticker symbol of the cryptocurrency to stake, e.g. ETH, SOL, etc. |
| network | string | yes | The blockchain network to stake on, e.g. Ethereum, Solana, etc. |
No output schema declared.
No examples provided.