Skip to main content
Glama
PaulieB14

Graph AAVE MCP

by PaulieB14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Graph AAVE MCP

Related Servers

  • graph-lending-mcp

    PaulieB14
    A
    license
    A
    quality
    C
    maintenance
    MCP server that exposes unified AI-friendly tools over Messari's standardized lending subgraphs on The Graph. One natural-language query → fan out across 40+ lending protocols on multiple chains → get back structured, comparable data.
    19
    11 npm
    1
    MIT

  • defi-mcp

    matiosera3-ops
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that gives AI agents direct, on-chain access to DeFi data on EVM chains — wallet balances, Aave v3 lending positions, and live token prices, with no centralized API in the middle.
    35 PyPI
    1
    MIT

  • graph-polymarket-mcp

    PaulieB14
    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
    68 npm
    4
    MIT

  • The Graph Token API MCP

    pinax-network
    A
    license
    Not graded
    quality
    F
    maintenance
    Official MCP server that turns The Graph’s Token API into a plug-and-play web3 data tool. Exposes ERC-20 & NFT metadata, balances, transfers, top-holder stats, prices, and more, allowing LLMs to run SQL queries on structured and indexed blockchain data.
    2
    Apache 2.0

  • graph-polymarket-mcp

    phon3
    A
    license
    B
    quality
    C
    maintenance
    MCP server to query Polymarket prediction market data via The Graph subgraphs and REST APIs, enabling AI agents to search markets, get live prices, order books, on-chain analytics, and trader profiles.
    32
    68 npm
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 40 tools

Disambiguation3/5

While each tool has a detailed description, there are several pairs with overlapping purposes (e.g., get_aave_liquidations vs get_risk_liquidations, get_aave_reserves vs get_v4_reserves, and multiple user-position tools). The high number of similar names could confuse an LLM despite the descriptions.

Naming Consistency2/5

Tool names use a mix of prefixes (get_, list_, find_, simulate_, query_) and sometimes include version (v4) or omit it. There is no consistent verb_noun pattern across the set, making it harder to infer behavior from the name alone.

Tool Count3/5

40 tools is on the high side, bordering on heavy. However, the server covers multiple AAVE versions, chains, and sub-domains (governance, risk, V4), so the count is somewhat justified. Some tools could be merged without loss of clarity.

Completeness4/5

The tool surface covers most expected queries: reserves, user positions, history, governance, risk, flash loans, liquidations, and raw subgraph access. Minor gaps exist (e.g., no cross-chain V2/V3 user summary, no tool to fetch all positions across chains), but overall it is comprehensive.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources