Compound Mcp
Let your coding agent pull Compound lending rates, supply, and borrow metrics while you build DeFi dashboards or yield-comparison tools.
Overview
io.github.junct-bot/compound-mcp is a MCP server for the Build phase that exposes eight tools for Compound lending rates, supply, and borrow data over streamable HTTP.
What is this MCP server?
- Eight MCP tools covering lending rates, market supply, and borrow-side data
- Hosted streamable-HTTP endpoint at compound.mcp.junct.dev—no local chain node required
- Version 1.1.0 server schema aligned with Model Context Protocol 2025-12-11
- GitHub source at junct-bot/compound-mcp for auditing the remote implementation
- Suited for agent-assisted due diligence and UI prototypes that cite live Compound markets
- 8 MCP tools for lending, supply, and borrow data
- Server version 1.1.0
- Remote URL: https://compound.mcp.junct.dev/mcp
What problem does it solve?
Agents cannot answer Compound market questions reliably when every lending metric requires custom RPC or subgraph code you have not written yet.
Who is it for?
Indie builders prototyping lending dashboards, yield bots, or research agents that need structured Compound data without maintaining their own indexer.
Skip if: Teams that need guaranteed mainnet write access, private mempool execution, or institutional compliance workflows—this server is read-oriented market data via MCP.
What do I get? / Deliverables
After you add the remote MCP URL, your agent can quote live Compound supply, borrow, and rate context inside planning chats and integration code.
- Eight registered Compound data tools available to your agent
- Agent-readable lending rate and supply/borrow context in chat and codegen sessions
- Repeatable remote endpoint instead of one-off subgraph scripts
Recommended MCP Servers
Journey fit
Remote MCP integration that wires live Compound protocol data into agent workflows during product build. Fits the integrations shelf because it exposes on-chain lending APIs as callable MCP tools rather than a one-off script.
How it compares
Remote finance-data MCP server, not a Compound smart-contract deployment skill or a local Hardhat workflow.
Common Questions / FAQ
Who is io.github.junct-bot/compound-mcp for?
Solo and indie developers building AI-assisted DeFi tools who want Compound lending metrics inside Claude Code, Cursor, or other MCP clients without custom subgraph glue.
When should I use io.github.junct-bot/compound-mcp?
Use it during build and validate when you need live supply, borrow, or rate context for prototypes, agent research, or integration code against Compound markets.
How do I add io.github.junct-bot/compound-mcp to my agent?
Register the streamable-HTTP remote https://compound.mcp.junct.dev/mcp in your MCP client config per the server.json entry, then restart the client so the eight tools appear.