Skip to main content
Glama
Tango86

graph-lido-mcp

by Tango86

Related Servers

Alternatives to graph-lido-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives any AI agent full access to Lido Finance's staking infrastructure through natural language. Stake ETH, manage positions, request withdrawals, and monitor protocol stats.
      -
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server for Everstake's non-custodial staking data across 130+ networks: live APY, uptime metrics, rewards calculator, integrations, security and compliance. Built for asset managers, custodians, and exchanges evaluating institutional staking.
      11
      1
      BSD 3-Clause
    • A
      license
      B
      quality
      B
      maintenance
      An MCP server that enables querying Polymarket prediction market data through The Graph subgraphs. It provides tools for accessing market stats, trader P\&L, user positions, and orderbook activity using AI agents.
      35
      77 npm
      4
      MIT

    TDQS

    A4/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a specific Lido protocol aspect (address activity, governance, withdrawals, etc.) with clearly distinct purposes. No overlapping functionality; even related tools like withdrawal requests and claims are well-separated.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with underscores (e.g., get_address_activity, get_governance_votes). The outlier query_lido_subgraph also follows verb_noun, maintaining the pattern.

    Tool Count5/5

    20 tools appropriately cover the multifaceted Lido protocol (staking, withdrawals, governance, node operations, etc.) without being overwhelming. Each tool earns its place.

    Completeness5/5

    The tool set comprehensively covers Lido's read-only surface: deposits, withdrawals, governance, monitoring stats, transfers, and edge cases via raw subgraph queries. No obvious gaps for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues