mcpbeat

Leverage MCP Server

xyz.spiralstake/leverage
answering

Leverage is answering right now. Last checked 16 min ago. It exposes 7 tools. Last commit 28 Jul 2026.

Leveraged-yield router on Morpho. List strategies, simulate, and build UNSIGNED txs.

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
364 ms
Response time
average over 24h
0
Stars
last commit 28 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 16 min ago.

run in your terminal
claude mcp add leverage --transport http https://api.spiralstake.xyz/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "leverage": {
      "url": "https://api.spiralstake.xyz/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.leverage]
url = "https://api.spiralstake.xyz/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "leverage": {
      "url": "https://api.spiralstake.xyz/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "leverage": {
      "url": "https://api.spiralstake.xyz/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

build
build_leverage_tx
Build the UNSIGNED transaction to open a leveraged position, for the given wallet to sign. Non-custodial: this server never signs, sends, or holds keys. The canonical output is the executable { approvals[], tx{to,data,value} } — sign and broadcast it directly (approvals first), plus the same position preview as simulate_leverage. meta.signingUrl is an optional one-click link for a human to sign in their own wallet. The embedded swap calldata is time-sensitive (see meta.expiresAt) — rebuild if stale.
build_manage_tx
Build the UNSIGNED transaction to adjust or close an OPEN position, for the given wallet to sign. Non-custodial (never signs/holds keys). Canonical output is the executable { approvals[], tx{to,data,value} } (sign/broadcast directly); meta.signingUrl is an optional link for a human to sign in their own wallet. Actions: 'close' (unwind fully), 'increase_leverage' (borrow to a higher LTV), 'add_collateral' (top up — pay in collateral or any token), 'remove_collateral' (withdraw), 'repay' (pay down debt; set full=true to clear it), 'borrow' (draw more loan token). Get the position `id` from get_positions. Swap calldata (close/increase/zap paths) is time-sensitive — see meta.expiresAt.
positions
get_positions
Read a wallet's open/closed Spiral leverage positions from chain state (read-only). For each: collateral/loan, leveraged collateral, net equity, debt, current LTV vs liquidation LTV (with headroom), current leverage, net USD value, and current leveraged APY. No cost-basis / realized P&L (those need off-chain history). Newest first.
prices
get_prices
Current USD prices for loan/collateral tokens (token address -> USD).
simulate
simulate_leverage
Preview opening a leveraged position — deterministic, read-only, no wallet needed. Returns the resulting leverage, effective LTV, leveraged collateral, expected leveraged APY, price impact, the auto-selected execution path, flash-loan size, and (if the flash loan exceeds direct market liquidity) the public-allocator reallocation fee. Numbers move with market prices.
strategies
list_strategies
List eligible Spiral leveraged-yield strategies with raw risk facts (collateral/borrow APY, leverage ladder, oracle type, exit-liquidity, LTVs). Optionally filter by collateral category.
strategy
get_strategy
Get one eligible strategy's full raw facts by its Morpho market id.

Endpoints

URLTransportStateLatencyChecked
https://api.spiralstake.xyz/mcp streamable-http answering 314 ms 16 min ago

Leverage — questions

Answers built from our own checks of this server.

What can Leverage do?
It exposes 7 tools, read directly from the server on our last check. Among them: build_leverage_tx, build_manage_tx, get_positions, get_prices, get_strategy, list_strategies and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Leverage working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 364 ms. The bar chart above shows every period we have measured.
How do I connect Leverage?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Leverage need an API key?
No. Leverage completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Leverage?
It answers our handshake in 364 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Leverage open source?
Yes — written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.