Ext Ops Panel
Open dashboard
Comparison

yieldprobe: DeFi intel for agents vs io.github.junct-bot/aave-mcp

yieldprobe: DeFi intel for agents is an MCP server published by yieldprobe.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.junct-bot/aave-mcp is an MCP server published by junct-bot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceyieldprobe: DeFi intel for agentsio.github.junct-bot/aave-mcp
Official MCP Registry Listed
Version: 0.2.0
No figure published
Not marked · First seen
Listed
Version: 1.1.0
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

yieldprobe: DeFi intel for agents vs io.github.junct-bot/aave-mcp
Factyieldprobe: DeFi intel for agentsio.github.junct-bot/aave-mcp
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Remote server (yieldprobe.com/mcp)Remote server (aave.mcp.junct.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/junct-bot/aave-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 11 h agoNot responding since 2026-10-15

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

yieldprobe: DeFi intel for agents

In its own words, on Official MCP Registry:

Paid DeFi data for agents via x402 on Base: yields, APY moves, stablecoin pegs, token risk.

io.github.junct-bot/aave-mcp

In its own words, on Official MCP Registry:

Aave - 6 tools for lending rates, supply, and borrow data

How to run each

yieldprobe: DeFi intel for agents As a remote MCP server

Claude Code
claude mcp add --transport http defi-intel https://yieldprobe.com/mcp

io.github.junct-bot/aave-mcp As a remote MCP server

Claude Code
claude mcp add --transport http aave-mcp https://aave.mcp.junct.dev/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of yieldprobe: DeFi intel for agents responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: yieldprobe: DeFi intel for agents · What it can do: io.github.junct-bot/aave-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built