graph-lido-mcp (Tango86/graph-lido-mcp) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 20 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
58/100

graph-lido-mcp

MCP server for querying Lido liquid staking protocol data via The Graph's decentralized network, providing tools for staking stats, APR, withdrawals, node operators, and governance.

→ Tango86/graph-lido-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Tango86

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: GRAPH_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes20 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

get_lido_stats

Get current Lido protocol statistics: total pooled ETH, total shares, unique holders, fee structure, and withdrawal queue status

get_staking_apr

Get Lido staking APR history from oracle reports. Returns APR (after fees), APR before fees, total rewards, MEV fees, and fee breakdown per report period

get_recent_submissions

Get recent stETH staking submissions (deposits). Shows who staked, how much ETH, shares received, and the effect on total pooled ether

get_recent_transfers

Get recent stETH token transfers. Track large stETH movements between addresses

get_node_operators

Get Lido node operators: names, staking limits, active status, stopped validators. These are the professional validator operators running Ethereum validators for Lido stakers

get_oracle_reports

Get Lido oracle completed reports: beacon chain balance, validator count per epoch. Oracle reports trigger reward distribution and stETH rebase

get_withdrawal_requests

Get recent stETH withdrawal requests. Shows who is requesting to unstake, how much stETH, and the shares being burned

get_withdrawal_claims

Get recent claimed (completed) withdrawals. Shows who received ETH back after the withdrawal queue processed their request

get_withdrawals_finalized

Get withdrawal finalization batches. Shows when the protocol finalized withdrawal request ranges, locking ETH and burning shares

get_governance_votes

Get Lido DAO governance votes (Aragon voting). Shows proposal metadata, execution status, and individual votes

get_vote_details

Get detailed voting records for a specific Lido DAO governance vote. Shows all individual voter addresses, their vote direction, and stake weight

get_easytrack_motions

Get Lido EasyTrack motions. EasyTrack is a lightweight governance mechanism for routine operations (budget allocations, reward programs) that do not require full DAO votes

get_shares_burns

Get stETH shares burn events. Shares are burned during withdrawal processing, reducing total supply

get_holder_shares

Look up the current stETH share balance for a specific address. Shares represent proportional ownership of the staking pool

get_top_holders

Get the largest stETH holders ranked by share balance. Shows addresses, share count, and estimated stETH value. Useful for tracking whale concentration and institutional holders

get_staking_net_flow

Calculate net staking flow: compare recent deposits (submissions) vs withdrawal requests to determine if Lido is growing or shrinking. Returns totals for each side and the net direction

get_address_activity

Get all Lido activity for a specific address: stETH balance, recent deposits, transfers (in/out), and withdrawal requests. Single view of an address's complete Lido interaction history

get_steth_ratio_history

Get the historical stETH/ETH exchange ratio derived from oracle reward reports. Shows how stETH appreciates over time relative to ETH as staking rewards accrue. The ratio should always be >= 1 and slowly increasing

get_lido_schema

Introspect the Lido subgraph GraphQL schema. Returns all available entity types and their fields. Useful for building custom queries

query_lido_subgraph

Run any raw GraphQL query against the Lido subgraph. Escape hatch for advanced queries not covered by other tools. Use get_lido_schema first to discover available entities and fields

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.12.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretGRAPH_API_KEY"": "your-api-key"
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

20/20 tools missing one or more hints — get_lido_stats (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_staking_apr (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_recent_submissions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

18/20 tool handlers declare input schemas (90%)

Declare an inputSchema with zod/joi/yup on every tool definition.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/tango86/graph-lido-mcp?variant=verified)](https://m8ven.ai/mcp/tango86/graph-lido-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 4c693bd3ccf089a91aacad2659a1f8cc76107c2d
code hash: 9be6228a2ddee228be21f2631a5f0841305a3c03e593bc3d4996745c2f8e070d
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client