Aave MCP by Junct
Hosted MCP server exposing tools mapped 1:1 to Aave's analytics API, no auth required.
- Sato Score39
- ChainsEthereum, Base +3
Aave MCP by Junct is an open-source MCP server by Junct on Ethereum, Base, Arbitrum and other chains, with last code activity on 2026-03-29 (Quiet). Sato Score 39/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →
Check what an install would ask of your keys, before you run it →Last commit Mar 29, 2026
Listed from junct.dev on 2026-07-19. Install: not attempted — no install path on record. Evidence →
Next step
Watch Aave MCP by Junct
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/mcpRun Sato Hub Preflight on junct-bot/aave-mcp before I use it.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
Aave MCP by Junct is a hosted Model Context Protocol server that gives AI agents structured access to Aave lending-protocol analytics across five EVM chains. Tools are deterministically generated from Aave's API spec, so an agent builder can query reserves, rates, and positions without writing custom API glue code.
Sato Score
39/100· LowHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 5/35
- Code transparency
- 16/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 12/15
- Independent verification
- 0/10
Evidence — listed vs checked · what the words mean
Listed from junct.dev on 2026-07-19. Install: not attempted — no install path on record.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Ethereum, Base, Arbitrum, Optimism, Polygon | self-reported | aave.mcp.junct.dev | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | junct.dev | as of 2026-10-21 |
| Recent activity | last commit 2026-03-29 | observed | github.com/junct-bot/aave-mcp | 2026-10-21 |
| MCP endpoint answers | did not answer our probe | observed | aave.mcp.junct.dev | 2026-10-21 |
| Daily check record | 0 of 50 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-20 |
| Built by | Junctconfidence 0.85 | self-reported | github.com/junct-bot/aave-mcp | as of 2026-07-28 |
| Creator profile | https://junct.devconfidence 0.80 | self-reported | github.com/junct-bot/aave-mcp | as of 2026-07-28 |
| Deploys as | Hostedconfidence 0.80 | self-reported | github.com/junct-bot/aave-mcp | as of 2026-07-28 |
| Docs | https://aave.mcp.junct.dev/llms.txtconfidence 0.80 | self-reported | github.com/junct-bot/aave-mcp | as of 2026-07-28 |
| Sato Score | 39/100 (Low)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-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.
Observed record — 91 daily checks since 2026-07-23
- Succeeded
- 0
- Failed
- 91
- Their error
- 0
- Unattributed
- 91
State changed on 2026-09-01 (unclear → unreachable from our probe).
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. The rate above leaves those checks out; the counts include them.
Last 30 days — to 2026-10-21, one point per UTC day
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, Optimism, Polygon
- Agent types
- MCP server
- Open source
- Yes
- Deploys as
- Hosted
- 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.
Where Aave MCP by Junct fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are MCPs? The Standard Way to Give Agents Tools
Listing History
Recorded changes to Aave MCP by Junct's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 26, 2026Sato Score tier: Medium → LowScore 47 → 39.
- Jul 28, 2026Auto-enriched: creator name, creator profile url, docs url, deployment options
- Jul 28, 2026Sato Score tier: Low → MediumScore 34 → 47.
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 20, 2026Edited: mcp endpoint url
- Jul 19, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Aave MCP by Junct
- Is Aave MCP by Junct open source?
- Yes. Aave MCP by Junct is open source; the repository is https://github.com/junct-bot/aave-mcp. Checked as of 2026-10-21.
- Which chains does Aave MCP by Junct support?
- Aave MCP by Junct lists support for Ethereum, Base, Arbitrum, Optimism, Polygon as of 2026-10-21.
- Is Aave MCP by Junct still maintained?
- The most recent code activity Sato Hub observed was on 2026-03-29 (last commit 2026-03-29), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Aave MCP by Junct?
- Sato Hub has no deploy spec for Aave MCP by Junct; follow the project's own documentation at https://aave.mcp.junct.dev/llms.txt.
- Is Aave MCP by Junct verified on Sato Hub?
- No independent verification is on record for Aave MCP by Junct; its verification status is "Unverified" and its Sato Score is 39 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Aave MCP by Junct — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/aave-mcp-junctData 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.