Lido MCP Server

lido-mcp npm v0.1.1

Published by 0xnilesh — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A MCP server that provides Claude AI and other MCP-compatible agents with real-time access to Lido liquid staking on Ethereum — stake, unstake, wrap, govern, and manage staking positions directly from a conversation.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 67

Each tool and what it can reach — statically extracted from the published source.

  • lido_get_token_inforeads sensitive data
  • lido_approveno sensitive capability
  • lido_approve_nftno sensitive capability
  • lido_can_voteno sensitive capability
  • lido_cast_voteno sensitive capability
  • lido_claim_single_withdrawalno sensitive capability
  • lido_claim_withdrawalno sensitive capability
  • lido_claim_withdrawals_tono sensitive capability
  • lido_convertno sensitive capability
  • lido_delegateno sensitive capability
Show 57 more tools ↓
  • lido_get_all_allowancesno sensitive capability
  • lido_get_allowanceno sensitive capability
  • lido_get_balanceno sensitive capability
  • lido_get_beacon_statsno sensitive capability
  • lido_get_bunker_modeno sensitive capability
  • lido_get_claimable_etherno sensitive capability
  • lido_get_contract_addressesno sensitive capability
  • lido_get_delegateno sensitive capability
  • lido_get_dual_governance_stateno sensitive capability
  • lido_get_easy_track_motionsno sensitive capability
  • lido_get_exchange_ratesno sensitive capability
  • lido_get_governance_overviewno sensitive capability
  • lido_get_l2_balancesno sensitive capability
  • lido_get_nft_ownerno sensitive capability
  • lido_get_node_operatorno sensitive capability
  • lido_get_node_operatorsno sensitive capability
  • lido_get_position_overviewno sensitive capability
  • lido_get_protocol_feeno sensitive capability
  • lido_get_protocol_infono sensitive capability
  • lido_get_rewardsno sensitive capability
  • lido_get_share_rateno sensitive capability
  • lido_get_staking_limitno sensitive capability
  • lido_get_staking_moduleno sensitive capability
  • lido_get_staking_modulesno sensitive capability
  • lido_get_supported_chainsno sensitive capability
  • lido_get_vaultno sensitive capability
  • lido_get_vault_hub_statsno sensitive capability
  • lido_get_voteno sensitive capability
  • lido_get_vote_countno sensitive capability
  • lido_get_vote_detailsno sensitive capability
  • lido_get_voter_stateno sensitive capability
  • lido_get_withdrawal_queue_infono sensitive capability
  • lido_get_withdrawal_requestsno sensitive capability
  • lido_get_withdrawal_statusno sensitive capability
  • lido_increase_allowanceno sensitive capability
  • lido_is_staking_pausedno sensitive capability
  • lido_list_vaultsno sensitive capability
  • lido_list_votesno sensitive capability
  • lido_monitor_positionno sensitive capability
  • lido_object_to_motionno sensitive capability
  • lido_prepare_transactionno sensitive capability
  • lido_request_withdrawalno sensitive capability
  • lido_revoke_all_approvalsno sensitive capability
  • lido_stakeno sensitive capability
  • lido_stake_and_wrapno sensitive capability
  • lido_statusno sensitive capability
  • lido_summaryno sensitive capability
  • lido_transferno sensitive capability
  • lido_transfer_ldono sensitive capability
  • lido_transfer_withdrawal_nftno sensitive capability
  • lido_undelegateno sensitive capability
  • lido_unwrapno sensitive capability
  • lido_vault_fundno sensitive capability
  • lido_vault_pause_depositsno sensitive capability
  • lido_vault_resume_depositsno sensitive capability
  • lido_vault_withdrawno sensitive capability
  • lido_wrapno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.1 latest A 96/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/lido-mcp/badge.svg)](https://mcptrustchecker.com/registry/lido-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/lido-mcp"><img src="https://mcptrustchecker.com/registry/lido-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/lido-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan lido-mcp --online

Use the free API → How scoring works

More in Finance & Commerce