io.github.PaulieB14/graph-aave-mcp
NPM · GRAPH-AAVE-MCP · SCANNED SEP 20
AAVE V2/V3 lending & governance MCP — 7 chains via The Graph subgraphs
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2291 tokens (~163/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.PaulieB14/graph-aave-mcp server?
io.github.PaulieB14/graph-aave-mcp runs locally as an npm package, launched with npx -y graph-aave-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · graph-aave-mcp
claude mcp add paulieb14-graph-aave-mcp -- npx -y graph-aave-mcp
{
"mcpServers": {
"paulieb14-graph-aave-mcp": {
"command": "npx",
"args": [
"-y",
"graph-aave-mcp"
]
}
}
} {
"servers": {
"paulieb14-graph-aave-mcp": {
"command": "npx",
"args": [
"-y",
"graph-aave-mcp"
]
}
}
} codex mcp add paulieb14-graph-aave-mcp -- npx -y graph-aave-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"paulieb14-graph-aave-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"graph-aave-mcp"
],
"enabled": true
}
}
} openclaw mcp add paulieb14-graph-aave-mcp --command npx --arg -y --arg graph-aave-mcp
mcp_servers:
paulieb14-graph-aave-mcp:
command: "npx"
args: ["-y", "graph-aave-mcp"] {
"McpServers": {
"paulieb14-graph-aave-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"graph-aave-mcp"
]
}
}
} assistant mcp add paulieb14-graph-aave-mcp -t stdio -c npx -a -y graph-aave-mcp
{
"mcpServers": {
"paulieb14-graph-aave-mcp": {
"command": "npx",
"args": [
"-y",
"graph-aave-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.77 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/graph-aave-mcp@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_aave_flash_loans ~119
Use this when the user asks about AAVE flash loans — 'Show me recent flash loans on Ethereum', 'What assets are flash-loaned most?', 'How much in flash loan fees has AAVE earned?'. Returns: initiator address, asset borrowed, amount, fee paid (totalFee), and timestamp. Flash loans must be borrowed and repaid within a single transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain identifier |
| first | number | – | Number of flash loan events to return (1–100, default 20) |
No output schema declared.
No examples provided.
get_aave_liquidations ~167
Use this when the user asks about AAVE liquidation events — 'Show me recent liquidations on Ethereum', 'Has address 0x... been liquidated?', 'Who are the top liquidators on Arbitrum?', 'What collateral is being seized most?'. Returns: liquidator address, liquidated user, collateral asset seized, debt asset repaid, amounts, and timestamp. Liquidations occur when a user's health factor drops below 1.0.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain identifier |
| first | number | – | Number of liquidation events to return (1–100, default 20) |
| liquidator | string | – | Optional: filter by liquidator address |
| userAddress | string | – | Optional: filter by the address that was liquidated |
No output schema declared.
No examples provided.
get_aave_reserve ~166
Use this when the user asks about a specific AAVE asset in detail — e.g. 'Tell me everything about USDC on Ethereum AAVE', 'What are the WETH borrow parameters?', 'What is the liquidation threshold for WBTC collateral?'. Returns full reserve config: current rates, TVL, LTV, liquidation parameters, lifetime stats (total borrows/repayments/liquidations), and token addresses. RATE CONVERSION: divide liquidityRate / variableBorrowRate by 1e27 * 100 for APY %.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain identifier |
| symbol | string | yes | Token symbol — case-insensitive (e.g. USDC, WETH, WBTC, DAI, USDT, LINK, AAVE) |
No output schema declared.
No examples provided.
get_aave_reserves ~232
Use this when the user asks about AAVE lending markets, available assets, supply APY, borrow APY, TVL, utilization rate, collateral factors, or liquidation thresholds on a specific chain. Returns all active reserves sorted by total liquidity (TVL). RATE CONVERSION: liquidityRate and variableBorrowRate are in RAY units (1e27). Supply APY % = liquidityRate / 1e27 * 100. Borrow APY % = variableBorrowRate / 1e27 * 100. Amounts are in native token units — divide by 10^decimals for human-readable. Ideal for: 'What assets can I lend on Arbitrum?', 'What is USDC supply rate on Base?', 'Show me all AAVE V3 markets on Polygon'.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain identifier (e.g. ethereum, base, arbitrum, polygon, optimism, avalanche). Use list_aave_chains to see all options. |
| includeInactive | boolean | – | Set true to include frozen, paused, or inactive reserves. Default false (active only). |
No output schema declared.
No examples provided.
get_aave_schema ~79
Use this to introspect the full GraphQL schema for any AAVE chain's subgraph. Returns all queryable root fields and their types. Useful before writing a custom query_aave_subgraph call, or to understand what data is available on a specific chain/version.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain identifier (includes 'governance') |
No output schema declared.
No examples provided.
get_aave_user_position ~185
Use this when the user asks about a wallet's AAVE position — 'What is my health factor?', 'What have I supplied to AAVE?', 'How much have I borrowed?', 'Am I at risk of liquidation?', 'Show me my collateral and debt on Arbitrum'. Returns all supplied assets (with aToken balances), all borrowed assets (variable + stable debt), collateral flags, and e-mode category. Health Factor ≈ sum(collateral_i * price_i * liqThreshold_i) / sum(debt_i * price_i). HF < 1.0 = liquidatable. Amounts in native token units — divide by 10^decimals.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain identifier |
| userAddress | string | yes | Ethereum wallet address of the user (0x..., lowercase). Returns empty arrays if address has no AAVE positions. |
No output schema declared.
No examples provided.
get_governance_proposals ~212
Use this when the user asks about AAVE governance — 'Show me recent AAVE governance proposals', 'What proposals are currently active?', 'What is the status of AAVE proposal #X?', 'Show me governance voting activity'. Queries the AAVE Governance V3 subgraph on Ethereum. Returns: proposal ID, creator, access level (1=short executor/2=long executor), current state, voting duration (seconds), for/against votes, title, and payload info. Proposal states: Created=0, Active=1, Queued=2, Executed=3, Failed=4, Cancelled=5, Expired=6.
| Name | Type | Req | Description |
|---|---|---|---|
| first | number | – | Number of proposals to return (1–50, default 10) |
| state | number | – | Optional: filter by state number. 0=Created, 1=Active, 2=Queued, 3=Executed, 4=Failed, 5=Cancelled, 6=Expired |
No output schema declared.
No examples provided.
get_proposal_votes ~113
Use this when the user asks about votes on a specific AAVE governance proposal — 'Who voted on proposal #X?', 'Show me the voting breakdown for this proposal', 'Which addresses voted against?'. Returns individual votes with: voter address, voting power, support (true=for/false=against), and timestamp.
| Name | Type | Req | Description |
|---|---|---|---|
| first | number | – | Number of votes to return (default 50) |
| proposalId | string | yes | AAVE governance proposal ID (numeric string, e.g. '185') |
No output schema declared.
No examples provided.
get_recent_borrows ~183
Use this when the user asks about recent borrowing activity on AAVE — 'Who has been borrowing USDC on Ethereum?', 'Show me recent WETH borrows on Arbitrum', 'What has address 0x... borrowed recently?', 'Show borrow volume by asset'. Returns borrow events with: borrower address, asset, raw amount, borrow rate, rate mode (variable=2/stable=1), and timestamp. Divide amount by 10^decimals for human-readable value.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain identifier |
| first | number | – | Number of borrow events to return (1–100, default 20) |
| reserveSymbol | string | – | Optional: filter by asset symbol (e.g. USDC, WETH, DAI) |
| userAddress | string | – | Optional: filter by borrower Ethereum address (0x...) |
No output schema declared.
No examples provided.
get_recent_supplies ~179
Use this when the user asks about recent deposit/supply activity on AAVE — 'Who has been supplying ETH on Base?', 'Show me recent USDC deposits on Polygon', 'What has address 0x... deposited recently?'. V3 chains use the 'supply' entity; V2 chains use 'deposit' — handled automatically. Returns: supplier address, asset symbol, raw amount, and timestamp. Divide amount by 10^decimals for human-readable value.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain identifier |
| first | number | – | Number of supply events to return (1–100, default 20) |
| reserveSymbol | string | – | Optional: filter by asset symbol (e.g. USDC, WETH, WBTC) |
| userAddress | string | – | Optional: filter by supplier address (0x...) |
No output schema declared.
No examples provided.
get_reserve_rate_history ~193
Use this when the user asks about historical AAVE rates or TVL trends — 'How has USDC supply rate changed over time?', 'Show me ETH borrow rate history on Polygon', 'What was the utilization rate last week?'. Returns timestamped snapshots of: liquidityRate, variableBorrowRate, stableBorrowRate, utilizationRate, availableLiquidity, totalLiquidity, totalCurrentVariableDebt. Rates are in RAY units (divide by 1e27 * 100 for APY %). Get the reserve ID from get_aave_reserves (the 'id' field = underlyingAsset + poolAddress).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain identifier |
| first | number | – | Number of historical snapshots to return (default 30) |
| reserveId | string | yes | Reserve ID — from get_aave_reserves 'id' field (concatenation of underlyingAsset address + pool address, lowercase) |
No output schema declared.
No examples provided.
list_aave_chains ~113
Use this when the user asks which AAVE chains are supported, wants to pick a network, or needs to discover available AAVE deployments. Returns all supported chains with their subgraph IDs, protocol version (V2/V3), chain name, 30-day query volume, and key entities. Chains: Ethereum, Base, Arbitrum, Polygon, Optimism, Avalanche, Fantom (V3 + V2 legacy), plus AAVE Governance V3. Always call this first if chain is ambiguous.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_aave_subgraph ~155
Use this when a pre-built tool doesn't cover the user's need — execute a raw GraphQL query against any AAVE chain's subgraph. Use get_aave_schema first to explore available entities and fields. Lending schema entities: reserves, userReserves, borrows, supplies (V3) / deposits (V2), repays, liquidationCalls, flashLoans, pool, protocol, reserveParamsHistoryItems. Governance schema entities: proposals, proposalVotes_collection, payloads, votingPortals, votingConfigs, proposalMetadata_collection.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain identifier (includes 'governance') |
| query | string | yes | GraphQL query string |
| variables | object | – | Optional GraphQL variables |
No output schema declared.
No examples provided.
simulate_health_factor ~195
Use this when the user wants to simulate how a price change affects their AAVE health factor — 'What happens to my health factor if ETH drops 20%?', 'How much can WBTC fall before I get liquidated?', 'Simulate a 30% drop in my collateral asset'. Fetches the user's full position, computes current health factor, then recalculates it after applying the specified price change to the target asset. Health Factor < 1.0 means the position is liquidatable.
| Name | Type | Req | Description |
|---|---|---|---|
| assetSymbol | string | yes | Symbol of the asset whose price changes (e.g. WETH, WBTC, USDC) |
| chain | string | yes | Chain identifier |
| priceChangePct | number | yes | Price change percentage — negative for drops, positive for gains. E.g. -20 means the asset price falls 20%. |
| userAddress | string | yes | Wallet address of the user (0x...) |
No output schema declared.
No examples provided.
What is the io.github.PaulieB14/graph-aave-mcp server?
io.github.PaulieB14/graph-aave-mcp is listed in the public MCP registry as io.github.PaulieB14/graph-aave-mcp. AAVE V2/V3 lending & governance MCP, 7 chains via The Graph subgraphs. This page covers its npm package (graph-aave-mcp).
Is the io.github.PaulieB14/graph-aave-mcp server safe to use?
io.github.PaulieB14/graph-aave-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.PaulieB14/graph-aave-mcp server expose?
io.github.PaulieB14/graph-aave-mcp exposes 14 tools: list_aave_chains, get_aave_reserves, get_aave_reserve, get_aave_user_position, simulate_health_factor, and 9 more. Their descriptions and schemas cost roughly 2,291 tokens of context every time the server is loaded.
Is the io.github.PaulieB14/graph-aave-mcp server still maintained?
io.github.PaulieB14/graph-aave-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.PaulieB14/graph-aave-mcp server under?
io.github.PaulieB14/graph-aave-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.