Lido Mcp
Let your agent query Lido staking, delegation, and rewards data while you build Ethereum yield dashboards or staking copilots.
Overview
Lido MCP is a MCP server for the Build phase that provides six Lido tools for staking, delegation, and rewards data to agents via streamable HTTP.
What is this MCP server?
- 6 MCP tools covering staking flows, delegation context, and rewards-oriented protocol data
- Hosted at lido.mcp.junct.dev with streamable-http transport
- Version 1.1.0 aligned to the 2025-12-11 MCP server schema
- Useful for explaining stETH yield mechanics in docs, support bots, or portfolio agents
- Complements lending and bridge MCP servers when modeling multi-protocol Ethereum stacks
- 6 MCP tools for staking, delegation, and rewards data
- Remote URL https://lido.mcp.junct.dev/mcp (streamable-http)
- Published server version 1.1.0
What problem does it solve?
Without a Lido-aware MCP layer, agents hallucinate APR, delegation, and rewards details when builders sketch staking features or user-facing explanations.
Who is it for?
Builders creating Ethereum staking dashboards, yield education bots, or agent workflows that must cite current Lido delegation and rewards context.
Skip if: Users seeking one-click stake transactions only, or teams with no MCP setup who prefer direct Lido SDK calls in application code alone.
What do I get? / Deliverables
Registering the Lido remote lets your agent ground staking and rewards answers in tool-backed protocol data while you code or write product copy.
- Six-tool Lido surface available to your agent during development
- More accurate staking and rewards narratives in docs and support flows
- Remote MCP configuration for lunct-bot/lido-mcp 1.1.0
Recommended MCP Servers
Journey fit
Liquid staking integrations are built when you connect product or agent layers to protocol state, which maps to Build rather than distribution-focused Launch phases. Lido MCP is a remote protocol bridge—exactly the integrations subphase where MCP servers replace bespoke REST glue in agent projects.
How it compares
Lido data MCP for agents, not a custody or key-management skill.
Common Questions / FAQ
Who is Lido MCP for?
Developers and indie founders building MCP-enabled agents or backends that need accurate Lido staking, delegation, and rewards information on Ethereum.
When should I use Lido MCP?
Use it while integrating liquid-staking features, drafting staking UX, or answering delegation questions inside your IDE during the Build phase.
How do I add Lido MCP to my agent?
Add https://lido.mcp.junct.dev/mcp as a streamable-http MCP server in your agent client configuration, then call the six Lido tools from prompts or automated tasks.