Claude
Desktop and Claude Code
Our MCP server gives Claude, Cursor and any compatible agent direct access to LP and lending positions: value, PnL, fees, health factor and history. Read-only, with the same key and credits as the API.
Nothing to install or host. The server runs on our side, and your client connects to it with an API key.
{
"mcpServers": {
"defiorbit": {
"url": "https://mcp.orbitcontrol.xyz/mcp",
"headers": {
"Authorization": "Bearer <API_KEY>"
}
}
}
}Desktop and Claude Code
Agent and chat
MCP-enabled assistants
Custom agents and internal tools
The agent picks the right tool, calls it and reads the result. You do not write queries or parse responses.
Every tool is read-only. None of them can move funds or change on-chain state.
52 tools across six protocols, plus wallet portfolio and account usage.
See all endpoints and credit costs →Use DeFi Orbit AI when an agent is doing the work. Use the API when your own code is.
Writing code with an AI assistant? The platform includes LLM instructions you can hand to it so it calls the REST API correctly.
Giving an agent access to financial data should not mean giving it access to funds.
No tool can sign, send or change anything on-chain.
The agent works from public wallet addresses. No private keys, no custody.
Calls draw from prepaid credits, so an agent cannot spend more than you loaded.
Give each agent its own key and turn it off whenever you need to.
It’s our hosted MCP server, which is the standard way to give an AI assistant tools it can call. Connect it to the assistant you already use and it can read your LP and lending positions with live data, so you can ask “which of my positions are out of range?” and get an answer from the chain, not from the model’s memory. There’s nothing to install or run on your side.
Any client that supports MCP, which today includes Claude Desktop, Claude Code and Cursor, among others. Setup is a few lines of configuration with the server address and your API key, and the connection guide in the docs covers each client.
No. DeFi Orbit AI uses the same API key and the same credits as the API, and each tool call costs the same as the endpoint behind it. Two of the 52 tools report your usage, so the assistant itself can tell you what you’ve spent.
No. All 52 tools are read-only: they return data and cannot sign, send, approve or change anything on-chain. The server never holds keys, so there’s nothing it could act with even if an agent asked.
You need an API key, which you create at platform.defiorbit.xyz. The Starter pack is 500 credits for $10, enough to connect an assistant and try every tool against real wallets.
Uniswap V3, Aerodrome and Orca for liquidity, and Aave V3, Morpho Blue and Kamino for lending, with portfolio tools for EVM wallets. That’s 52 tools in total, and new API endpoints become tools as they ship.
Anything the data can answer: the fees a position has earned this month, which positions are out of range, the health factor on a lending position, or a summary of a wallet’s performance. The assistant picks the right tools and combines them, so you ask in plain language rather than learning endpoints.
DeFi Orbit returns data only to the client that requested it. What happens next depends on the assistant you use, since its model provider processes the conversation, so choose a client whose data terms you’re comfortable with.
Start with 500 credits for $10. No subscription.