Developer Tools
spiralstake.xyz
Provides access to Morpho leveraged yield strategies, including data retrieval, price feeds, simulation, and transaction building for DeFi positions.
ENDPOINT 1
https://api.spiralstake.xyz/mcp
MCP server metadata
- Name
- spiralstake
- Version
- 0.1.0
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/zero-APY markets are hidden). Numbers are a snapshot ('asOf'); they move. This is not financial advice. Execution is non-custodial. simulate_leverage previews a position (deterministic, no wallet). build_leverage_tx / build_manage_tx return an UNSIGNED transaction for the user's own wallet to sign — this server never signs, sends, or holds keys. It auto-selects the path (direct vs zap-swap, and public-allocator reallocation when liquidity is thin) in the background, just like the app. The canonical output is the executable payload: sign and broadcast approvals[] first, then tx{to,data,value} — directly, with any wallet, signer library, or Safe. meta.signingUrl is an ADDITIONAL convenience for human-driven sessions (a one-click link to review and sign in the app); surface it when a human is in the loop, but autonomous callers should execute the payload. Always simulate before building, and rebuild if meta.expiresAt has passed.
Known tools 7
list_strategiesList eligible Spiral leveraged-yield strategies with raw risk facts (collateral/borrow APY, leverage ladder, oracle type, exit-liquidity, LTVs).
Inferred read-onlysimulate_leveragePreview opening a leveraged position — deterministic, read-only, no wallet needed.
Inferred read-onlybuild_leverage_txBuild the UNSIGNED transaction to open a leveraged position, for the given wallet to sign.
Inferred read-onlyget_positionsRead a wallet's open/closed Spiral leverage positions from chain state (read-only).
Inferred read-onlybuild_manage_txBuild the UNSIGNED transaction to adjust or close an OPEN position, for the given wallet to sign.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.spiralstake]
url = "https://api.spiralstake.xyz/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"spiralstake": {
"type": "http",
"url": "https://api.spiralstake.xyz/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: spiralstake
Remote MCP URL: https://api.spiralstake.xyz/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"spiralstake": {
"url": "https://api.spiralstake.xyz/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"spiralstake": {
"type": "http",
"url": "https://api.spiralstake.xyz/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "spiralstake",
"transport": "streamable-http",
"url": "https://api.spiralstake.xyz/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.