Lido Mcp

io.github.junct-botPublished by GitHub account junct-botv1.1.0Updated Nov 2, 2026

Lido - 6 tools for staking, delegation, and rewards data

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Hosted MCP server exposing six Lido staking, delegation and rewards data tools so an assistant can query Lido protocol information.

What you can do
  • Query Lido staking data through the hosted API
  • Look up delegation information
  • Retrieve rewards data
  • Each of the six tools maps one-to-one to a real Lido API endpoint, generated from the Lido API specification.
When to use it
Useful when an assistant needs Lido protocol staking, delegation or rewards figures during crypto or DeFi research, without building its own API integration.
Requirements
A remote streamable HTTP endpoint at lido.mcp.junct.dev/mcp; no authentication, API key or environment variables are required. Network access to the hosted endpoint is needed.
Before you install
The server is a third-party hosted service that relays requests to the Lido API, so queries go to that operator. It is described as read-only data access, but confirm tool behavior before relying on figures for financial decisions.

Installation

In SourceWeft

  1. Open Lido Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.junct-bot%2Flido-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lido": {
      "type": "http",
      "url": "https://lido.mcp.junct.dev/mcp"
    }
  }
}

README

Lido MCP Server

MCP server for Lido. Agent-ready API for Lido.

Hosted at lido.mcp.junct.dev/mcp. Free to use. No auth. No API key required.

Part of Junct — the agent-readiness layer for the crypto stack.

Quick Start

Add to your MCP client config (Claude Desktop, Cursor, Windsurf):

json
{  "mcpServers": {    "lido": {      "url": "https://lido.mcp.junct.dev/mcp",      "transport": "streamable-http"    }  }}

About

This MCP server is deterministically generated from the Lido API specification. Every tool maps 1:1 to a real API endpoint — no hallucinated endpoints, no phantom tools.

Links

Keywords

Lido, MCP server, DeFi, AI agent, agent-ready API, crypto tools, Model Context Protocol, hosted MCP

Source: README.md at commit 2f9f249

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.