Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

xyz.spiralstake/leverage

REMOTE · API.SPIRALSTAKE.XYZ

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

−1 this week 84 Trust /100

Last scanned (20 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security77
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3052 tokens (~305/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://api.spiralstake.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.spiralstake.xyz CN=YE2,O=Let's Encrypt,C=US 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA384 5d8098c2839bd5aad5c2a9642fa0d71386b
SANs: api.spiralstake.xyz
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.spiralstake.xyz. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
spiralstake.xyz. present 1045 13 Verified
api.spiralstake.xyz. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.spiralstake.xyz/mcp Verified 200
http (plaintext) http://api.spiralstake.xyz/mcp HTTPS enforced 301 https://api.spiralstake.xyz/mcp
MCP tools · 10 exposed · ~2,484 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
build_equity_deposit_tx ~332

Build the UNSIGNED call batch to deposit into a stock + yield equity vault, for the given wallet to sign. Non-custodial. Returns `calls[]` (approve USDG → router, authorize the router on Morpho, the one-call equityEntry, revoke) to submit as ONE atomic batch (EIP-5792 wallet_sendCalls / Safe), plus the same preview as simulate_equity_deposit. meta.signingUrl is a one-click link for a human to sign in the app. Swap calldata is time-sensitive (meta.expiresAt).

NameTypeReqDescription
amountstringyesDeposit amount in human units of the vault's deposit token (USDG), e.g. '10000'.
chainIdinteger–Chain to target. Supported: 1, 4663. Default: 1.
slippagenumber–Swap slippage ratio. Default 0.01 (the app's setting for vaults), capped at 0.01.
stockLtvPctstring–Stock-leg LTV percent to borrow at (e.g. '50'). Default: the vault's targetLtvPct. Capped at 88% of the stock market's liquidation LTV (55 on a 62.5% market) — a higher value is refused, not clamped.
strategyIdstringyesThe vault's id from list_strategies (starts with 'equity-').
userAddressstringyesThe wallet that will sign and send; the stock leg and yield loop are opened for it.

No output schema declared.

No examples provided.

build_equity_exit_tx ~271

Build the UNSIGNED call batch to fully unwind an OPEN equity vault (from get_positions.equityPositions): close each of its yield loops, then one self-funded router call repays the stock debt, withdraws the stock, swaps it to USDG and returns the proceeds. Submit as ONE atomic batch. Non-custodial; the vault's yield loop cannot be closed alone through build_manage_tx. Only the vault's own loop(s) are closed: those get_positions attributes unambiguously, or exactly the ones you pass in yieldPositionIds. Always read meta.closedYieldPositionIds.

NameTypeReqDescription
chainIdinteger–Chain to target. Supported: 1, 4663. Default: 1.
slippagenumber–Swap slippage ratio. Default 0.01, capped at 0.01.
strategyIdstringyesThe vault's id ('equity-0x…').
userAddressstringyesWallet that owns the vault and will sign.
yieldPositionIdsarray–The yield loop id(s) to close with the stock leg (from get_positions). Optional when the vault's yieldLoopMatch is tagged/basis/mixed; REQUIRED when it is 'ambiguous'. Nothing outside this list is cl…

No output schema declared.

No examples provided.

build_leverage_tx ~362

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.

NameTypeReqDescription
amountstringyesAmount of payToken in human units (e.g. '10000' for 10,000 USDC).
chainIdinteger–Chain to target. Supported: 1, 4663. Default: 1.
desiredLtvstring–Target LTV percent, e.g. '66.67'. Provide this OR leverage.
leveragenumber–Target leverage, e.g. 3. Provide this OR desiredLtv.
payTokenstringyesAddress of the token you pay in. May be the collateral (opened directly) or any other token (zapped: swapped to collateral first). Native ETH = the zero address 0x0000…0000.
slippagenumber–Swap slippage as a ratio (0.005 = 0.5%). Default 0.005, capped at 0.01.
strategyIdstringyesMorpho market id of the strategy (from list_strategies / get_strategy).
userAddressstringyesThe wallet address that will sign and send. Approvals and onBehalfOf are built for it.

No output schema declared.

No examples provided.

build_manage_tx ~416

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.

NameTypeReqDescription
actionstringyesWhat to do to the position.
amountstring–Human-units amount. Required for add_collateral/remove_collateral/repay/borrow.
chainIdinteger–Chain to target. Supported: 1, 4663. Default: 1.
desiredLtvstring–increase_leverage: target LTV percent (e.g. '80'). Provide this OR leverage.
fullboolean–repay only: clear the entire remaining debt.
idintegeryesOn-chain position index, from get_positions (its `id`).
leveragenumber–increase_leverage: target leverage. Provide this OR desiredLtv.
payTokenstring–Token to pay in (add_collateral/repay). Collateral/loan = direct; any other = zapped. ETH = zero address.
slippagenumber–Swap slippage ratio (0.005 = 0.5%). Default 0.005, capped at 0.01.
userAddressstringyesWallet that owns the position and will sign.

No output schema declared.

No examples provided.

get_positions ~157

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. `equityPositions` lists the wallet's open equity vaults (stock leg + the yield loop(s) it funds); those loops are excluded from `positions`.

NameTypeReqDescription
chainIdinteger–Chain to target. Supported: 1, 4663. Default: 1.
userAddressstringyesWallet address to read positions for.

No output schema declared.

No examples provided.

get_prices ~91

Current USD prices of every loan and collateral token the chain's strategies use (token address -> USD), including equity-vault stocks. Loan tokens are priced from CoinGecko; collateral from the market oracle × its loan token's price — the same figures the strategies' priceUsd fields carry.

NameTypeReqDescription
chainIdinteger–Chain to target. Supported: 1, 4663. Default: 1.

No output schema declared.

No examples provided.

get_strategy ~68

Get one eligible strategy's full raw facts by its Morpho market id.

NameTypeReqDescription
chainIdinteger–Chain to target. Supported: 1, 4663. Default: 1.
idstringyesMorpho market id (0x followed by 64 hex chars).

No output schema declared.

No examples provided.

list_strategies ~198

List eligible Spiral strategies on a chain with raw risk facts (collateral/borrow APY, leverage ladder, oracle type, exit liquidity, LTVs, curator). Mainnet (1): correlated yield loops on stables, ETH, BTC and Pendle PTs. Robinhood Chain (4663): stable loops on USDG, directional perps (spiralHints.profile 'leveraged_perp' — APYs are financing carry only) and stock + yield equity vaults (profile 'equity_yield_vault', ids start with 'equity-'). Optionally filter by collateral category.

NameTypeReqDescription
categorystring–Filter by collateral category: 'stable', 'ETH', 'BTC', 'stable-PT', 'stocks' (equity vaults), 'Other' (perps).
chainIdinteger–Chain to target. Supported: 1, 4663. Default: 1.

No output schema declared.

No examples provided.

simulate_equity_deposit ~296

Preview depositing USDG into a stock + yield equity vault — deterministic, read-only, no wallet. You end up 1x long the stock (held as your own Morpho collateral), with `stockLtvPct` of its value borrowed as USDG and flash-looped into the vault's yield strategy. Returns the stock received, the borrow, the stock liquidation price and headroom, the yield leg's size/leverage/APY, the net APY at that LTV, fees and price impact per leg.

NameTypeReqDescription
amountstringyesDeposit amount in human units of the vault's deposit token (USDG), e.g. '10000'.
chainIdinteger–Chain to target. Supported: 1, 4663. Default: 1.
slippagenumber–Swap slippage ratio. Default 0.01 (the app's setting for vaults), capped at 0.01.
stockLtvPctstring–Stock-leg LTV percent to borrow at (e.g. '50'). Default: the vault's targetLtvPct. Capped at 88% of the stock market's liquidation LTV (55 on a 62.5% market) — a higher value is refused, not clamped.
strategyIdstringyesThe vault's id from list_strategies (starts with 'equity-').

No output schema declared.

No examples provided.

simulate_leverage ~293

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.

NameTypeReqDescription
amountstringyesAmount of payToken in human units (e.g. '10000' for 10,000 USDC).
chainIdinteger–Chain to target. Supported: 1, 4663. Default: 1.
desiredLtvstring–Target LTV percent, e.g. '66.67'. Provide this OR leverage.
leveragenumber–Target leverage, e.g. 3. Provide this OR desiredLtv.
payTokenstringyesAddress of the token you pay in. May be the collateral (opened directly) or any other token (zapped: swapped to collateral first). Native ETH = the zero address 0x0000…0000.
slippagenumber–Swap slippage as a ratio (0.005 = 0.5%). Default 0.005, capped at 0.01.
strategyIdstringyesMorpho market id of the strategy (from list_strategies / get_strategy).

No output schema declared.

No examples provided.

Install

How do I install the xyz.spiralstake/leverage MCP server?

xyz.spiralstake/leverage is a hosted endpoint at https://api.spiralstake.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.spiralstake.xyz

# add to Claude Code
claude mcp add --transport http xyz-spiralstake-leverage 'https://api.spiralstake.xyz/mcp'
Common questions

What is the xyz.spiralstake/leverage MCP server?

xyz.spiralstake/leverage is an MCP server listed in the public MCP registry as xyz.spiralstake/leverage. Leveraged-yield router on Morpho. List strategies, simulate, and build UNSIGNED txs. This page covers its hosted endpoint (https://api.spiralstake.xyz/mcp).

Is the xyz.spiralstake/leverage MCP server safe to use?

xyz.spiralstake/leverage scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the xyz.spiralstake/leverage MCP server expose?

xyz.spiralstake/leverage exposes 10 tools: list_strategies, get_strategy, get_prices, simulate_leverage, build_leverage_tx, and 5 more. Their descriptions and schemas cost roughly 2,484 tokens of context every time the server is loaded.

Does the xyz.spiralstake/leverage MCP server require authentication?

No. We connected to xyz.spiralstake/leverage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the xyz.spiralstake/leverage MCP server still maintained?

xyz.spiralstake/leverage is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.