mcp.everstake.one
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 353 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-003 | OK | — | 362 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-004 | OK | — | 416 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-005 | OK | — | 376 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-006 | OK | — | 394 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-007 | OK | — | 412 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-008 | OK | — | 516 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-009 | OK | — | 375 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-010 | OK | — | 402 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-011 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-012 | OK | — | 489 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-013 | OK | — | 408 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-014 | OK | — | 445 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-015 | OK | — | 113 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-016 | OK | — | 151 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-017 | OK | — | 150 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-018 | OK | — | 120 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-019 | OK | — | 157 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-020 | OK | — | 159 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-021 | OK | — | 171 | 11 | 0b84eb58370424a3… | |
| REL-SNAP-022 | OK | — | 136 | 11 | 0b84eb58370424a3… |
Identity
- Record key
mcp.everstake.one— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- one.everstake/mcp What the registry said when we swept it, as observed by us — not evidence that the registry was correct, that the name belongs to whoever registered it, or that it still resolves. Not covered by the chain: no inclusion proof reaches this field.
- Name reported by the server
- Everstake MCP Self-reported and unverified — never used as identity.
Verifying this record
Each observation above carries a merkle leaf in the published snapshot it belongs to. Verify the chain explains how to walk a leaf to a published root without taking our word for any of it.