Lido MCP
MCP server for Lido liquid staking: stake, unstake, wrap, vote, and monitor yields on Ethereum.
- Sato Score48
- ChainsEthereum
Lido MCP is an open-source MCP server on Ethereum, with last code activity on 2026-03-23 (Quiet). Latest release on 2026-03-21. Sato Score 48/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →
See how to install Lido MCP →Last commit Mar 23, 2026 · Last release Mar 21, 2026 · ★ 2
Listed from github.com/ghost-clio/lido-mcp on 2026-07-19. Install: not attempted. Evidence →
Next step
Watch Lido MCP
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on ghost-clio/lido-mcp before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Lido MCP is a Model Context Protocol server built with viem that lets AI agents stake and unstake ETH, wrap/unwrap stETH, vote in Lido governance, and monitor vault yields on Ethereum mainnet. It includes a dry-run mode for transaction simulation and integrates with Claude Desktop and Cursor.
Sato Score
48/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 17/20
- Interface verifiability
- 0/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 8/15
- Independent verification
- 3/10
Evidence — listed vs checked · what the words mean
Listed from github.com/ghost-clio/lido-mcp on 2026-07-19. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Ethereum | self-reported | github.com/ghost-clio/lido-mcp | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | github.com/ghost-clio/lido-mcp | as of 2026-10-21 |
| Recent activity | last release 2026-03-21 · last commit 2026-03-23 | observed | github.com/ghost-clio/lido-mcp | 2026-10-21 |
| Install works | documented by the project, not run by Sato Hubnot attempted: the run did not complete and the log named no cause we could attribute | self-reported | github.com/ghost-clio/lido-mcp | as of 2026-10-19 |
| Website answers | answered (HTTP 200) | observed | github.com/ghost-clio/lido-mcp | 2026-10-21 |
| Daily check record | 90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-20 |
| Works with | Claude Desktop, Cursorconfidence 0.85 | self-reported | github.com/ghost-clio/lido-mcp | as of 2026-09-15 |
| Sato Score | 48/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-21 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — not run by us — the run did not complete and the log named no cause we could attribute
Runtime: Node.js (built to dist/index.js)
git clone https://github.com/ghost-clio/lido-mcp.git
cd lido-mcp
npm install
npm run build
{"mcpServers": {"lido": {"command": "node", "args": ["/path/to/lido-mcp/dist/index.js"], "env": {"ETH_RPC_URL": "https://eth.llamarpc.com", "ETH_PRIVATE_KEY": "0x..."}}}}You supply: ETH_RPC_URL — optional, defaults to https://eth.llamarpc.com, ETH_PRIVATE_KEY — RISK: hex-encoded private key, only required for write operations (staking/voting transactions); read-only tools work without it per the README
claude mcp add satohub-lido-mcp-ghost-clio -- node /path/to/lido-mcp/dist/index.js
A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-10-19. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-23
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-21, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Ethereum
- Agent types
- MCP server
- Open source
- Yes
- Pricing
- Free/open source
- Works with
- Claude Desktop, Cursor
- Last checked
- 2026-10-21
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Listing History
Recorded changes to Lido MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 19, 2026Verified: deploy spec
- Sep 15, 2026Auto-enriched: supported integrations
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 19, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Lido MCP
- Is Lido MCP open source?
- Yes. Lido MCP is open source under the MIT license; the repository is https://github.com/ghost-clio/lido-mcp. Checked as of 2026-10-21.
- Which chains does Lido MCP support?
- Lido MCP lists support for Ethereum as of 2026-10-21.
- Is Lido MCP still maintained?
- The most recent code activity Sato Hub observed was on 2026-03-23 (last commit 2026-03-23, last release 2026-03-21), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Lido MCP?
- Node.js (built to dist/index.js). Install: git clone https://github.com/ghost-clio/lido-mcp.git && cd lido-mcp && npm install && npm run build. Entry: {"mcpServers": {"lido": {"command": "node", "args": ["/path/to/lido-mcp/dist/index.js"], "env": {"ETH_RPC_URL": "https://eth.llamarpc.com", "ETH_PRIVATE_KEY": "0x..."}}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (node /path/to/lido-mcp/dist/index.js (stdio)).
- Is Lido MCP verified on Sato Hub?
- No independent verification is on record for Lido MCP; its verification status is "Unverified" and its Sato Score is 48 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Lido MCP — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/lido-mcp-ghost-clioData last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.