Skip to content
External endpointresponds

leverage

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

Endpoint URL
https://api.spiralstake.xyz/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
248 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
xyz.spiralstake/leverage

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
spiralstake
Version
0.1.0
Capability keys
tools
Tool names
list_strategies, get_strategy, get_prices, simulate_leverage, build_leverage_tx, get_positions, build_manage_tx
Instructions excerpt

Spiral Stake exposes leveraged-yield ("looping") strategies powered by Morpho. Ethereum mainnet is the default; pass chainId to target another supported chain (see a tool's chainId field). Every field is a raw, unit-labeled fact — the only opinion is namespaced under 'spiralHints' and always ships its thresholds, so you can override it. How to read the facts (mechanics, not advice): - carry = collateralApyPct - netBorrowApyPct; leverage multiplies it. Negative carry can still leave a positive leverageApyPct because the 1x base yield dominates — read the leverageLadder, don't infer. - oracle.type: 'nav' shrugs off DEX depegs; 'market' can liquidate on a depeg even if the collateral still redeems 1:1. Weigh against ltvPct.liquidation headroom. - exitLiquidity.slippagePct is measured per USD size; null = no route at that size (negative = price improvement). maxLeverage is a liquidity bound, not a safety bound. Only eligible strategies are returned (thin/near-maturity/no-swap-route/ze

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 48ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 243ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 248ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 248ms