Remote MCP · Endpoint
com.everstake/mcp MCP server
No. com.everstake/mcp answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.everstake.com/
The last check completed an MCP handshake.
- Registry name
- com.everstake/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 396 ms
- Tools exposed
- 11 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- MCP server connecting AI agents to non-custodial staking data across 130+ networks.
- Repository
- https://github.com/everstake/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 396 ms |
| 18 hours ago | Handshake completed | 312 ms |
| 2 days ago | Handshake completed | 344 ms |
| 3 days ago | Handshake completed | 310 ms |
| 4 days ago | Handshake completed | 310 ms |
| 5 days ago | Handshake completed | 348 ms |
| 6 days ago | Handshake completed | 382 ms |
| 7 days ago | Handshake completed | 360 ms |
| 10 days ago | Handshake completed | 336 ms |
| 13 days ago | Handshake completed | 365 ms |
| 15 days ago | Handshake completed | 308 ms |
| 17 days ago | Handshake completed | 335 ms |
| 19 days ago | Handshake completed | 345 ms |
| 21 days ago | Handshake completed | 340 ms |
| 23 days ago | Handshake completed | 340 ms |
| 25 days ago | Handshake completed | 308 ms |
| 27 days ago | Handshake completed | 350 ms |
| 28 days ago | Handshake completed | 318 ms |
| 29 days ago | Handshake completed | 324 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with com.everstake/mcp and makes no claim about it beyond what these checks measured.