Sato Hub
Data Tool

graph-aave-mcp

MCP server querying Aave V2/V3/V4 lending and governance data across 7 chains via The Graph.

  • Sato Score69
  • ChainsEthereum, Base +4
ActiveUnverifiedActive · 6d ago

graph-aave-mcp is an open-source data tool on Ethereum, Base, Arbitrum and other chains, with last code activity on 2026-10-15 (Active). Latest release on 2026-03-30. Sato Score 69/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →

See how to install graph-aave-mcp →

Last commit Oct 15, 2026 · Last release Mar 30, 2026 · ★ 2

Listed from github.com/PaulieB14/graph-aave-mcp on 2026-07-19. Install: reproduced by Sato Hub on 2026-07-21. Evidence →

Website ↗GitHub ↗

Next step

Watch graph-aave-mcp

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on paulieb14/graph-aave-mcp before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

graph-aave-mcp aggregates Aave lending, liquidation-risk, and governance data from The Graph subgraphs plus the Aave V4 API, exposing 50+ tools across 7 EVM chains. It's published to the MCP Registry and NPM, giving agent builders deeper historical and cross-chain governance coverage than REST-only Aave integrations.

Sato Score

69/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
17/20
Interface verifiability
8/10
Docs & demo
0/10
Listing transparency & provenance
6/15
Independent verification
3/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

View verification & embed badge →History →How the Sato Score works

Sato Check

v4.3.1 · as of 2026-10-16
Does it take your key?
No key read found
Does your key leave?
Not yet run
Can it move funds on its own?
Unknown
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from github.com/PaulieB14/graph-aave-mcp on 2026-07-19. Install: reproduced by Sato Hub on 2026-07-21.

ClaimValueEvidenceSourceChecked
Chains supportedEthereum, Base, Arbitrum, Polygon, Optimism, Avalancheself-reportedgithub.com/PaulieB14/graph-aave-mcpas of 2026-10-21
Verification statusUnverified — not independently reviewedself-reportedgithub.com/PaulieB14/graph-aave-mcpas of 2026-10-21
Recent activitylast release 2026-03-30 · last commit 2026-10-15observedgithub.com/PaulieB14/graph-aave-mcp2026-10-21
Install worksreproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour✓ reproducedgithub.com/PaulieB14/graph-aave-mcp2026-07-21
Website answersanswered (HTTP 200)observedgithub.com/PaulieB14/graph-aave-mcp2026-10-21
Daily check record90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-20
Takes your keyno private-key read found in what we readtracedsatohub.ai2026-10-16
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-10-16
Sato Score69/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-21

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — reproduced in a container Jul 21, 2026

Runtime: Node.js (npm package "graph-aave-mcp")

claude mcp add graph-aave -- npx -y graph-aave-mcp
export GRAPH_API_KEY=your-key-here
git clone https://github.com/PaulieB14/graph-aave-mcp.git
cd graph-aave-mcp
npm install
npm run build
{"mcpServers": {"graph-aave": {"command": "npx", "args": ["-y", "graph-aave-mcp"], "env": {"GRAPH_API_KEY": "your-api-key-here"}}}}

You supply: GRAPH_API_KEY — required for The Graph subgraph tools (V2/V3/Liquidation Risk/V4 Omnigraph); free tier at thegraph.com/studio, 100K queries/month; Aave V4 API tools need no key

Add to CursorAdd to VS Code
claude mcp add satohub-graph-aave-mcp -- npx -y graph-aave-mcp

A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-07-21. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-23

100%of 91 checks since 2026-07-23 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-21, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
69
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Ethereum, Base, Arbitrum, Polygon, Optimism, Avalanche
Agent types
MCP server
Open source
Yes
Last checked
2026-10-21

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#mcp#aave#the-graph#governance#lending#data

Where graph-aave-mcp fits

TradingData

Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are MCPs? The Standard Way to Give Agents Tools

See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to graph-aave-mcp's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Jul 24, 2026
    Sato Hub began tracking this listing
  2. Jul 21, 2026
    Verified: deploy spec
  3. Jul 19, 2026
    Listed on Sato Hub

Compared with

Alternatives to graph-aave-mcp →

Appears in

Related Resources

Coinbase AgentKit

Active
Framework

Coinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.

BaseEthereumMultichain
Active★ 1.3k

Hyperliquid

Active
VenueVerified

Onchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.

MultichainHyperliquid
Recent★ 506▸ Jun 2023

Model Context Protocol (MCP)

Active
Standard

Anthropic's open standard for connecting AI systems to external tools and data sources.

Unknown
Active★ 9.5k

Reference

QuestionsShowHide

Questions people ask about graph-aave-mcp

Is graph-aave-mcp open source?
Yes. graph-aave-mcp is open source under the MIT license; the repository is https://github.com/PaulieB14/graph-aave-mcp. Checked as of 2026-10-21.
Which chains does graph-aave-mcp support?
graph-aave-mcp lists support for Ethereum, Base, Arbitrum, Polygon, Optimism, Avalanche as of 2026-10-21.
Is graph-aave-mcp still maintained?
The most recent code activity Sato Hub observed was on 2026-10-15 (last commit 2026-10-15, last release 2026-03-30), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run graph-aave-mcp?
Node.js (npm package "graph-aave-mcp"). Install: claude mcp add graph-aave -- npx -y graph-aave-mcp && export GRAPH_API_KEY=your-key-here && git clone https://github.com/PaulieB14/graph-aave-mcp.git && cd graph-aave-mcp && npm install && npm run build. Entry: {"mcpServers": {"graph-aave": {"command": "npx", "args": ["-y", "graph-aave-mcp"], "env": {"GRAPH_API_KEY": "your-api-key-here"}}}}. Sato Hub reproduced this install in a container on 2026-07-21. It runs as an MCP server (npx -y graph-aave-mcp (stdio)).
Is graph-aave-mcp verified on Sato Hub?
Sato Hub holds one earned check for graph-aave-mcp: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 69 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "graph-aave-mcp — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/graph-aave-mcp

Data last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.