Skip to content

leverage MCP server

xyz.spiralstake/leveragespiralstake.xyzstreamable-httpv0.1.1Scanned

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

10 tools: 4 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 4 write, 6 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the leverage MCP server can do

The leverage MCP server is published by spiralstake.xyz, a domain the MCP Registry verified. It has 10 tools. It can create or change data (4 tools: build_leverage_tx, build_manage_tx, build_equity_deposit_tx and build_equity_exit_tx), but cannot delete data. 6 tools only read.

2 tools read private data (get_prices and simulate_equity_deposit).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Changes things 4Claude Code: ask
  • build_equity_deposit_txBuild the UNSIGNED call batch to deposit into a stock + yield equity vault, for the given wallet to sign.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Build Equity Vault Deposit
    • readOnlyHint: false
    • destructiveHint: false
  • build_equity_exit_txBuild 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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Build Equity Vault Exit
    • readOnlyHint: false
    • destructiveHint: false
  • build_leverage_txBuild the UNSIGNED transaction to open a leveraged position, for the given wallet to sign.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Build Leverage Transaction
    • readOnlyHint: false
    • destructiveHint: false
  • build_manage_txBuild the UNSIGNED transaction to adjust or close an OPEN position, for the given wallet to sign.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Build Manage Transaction
    • readOnlyHint: false
    • destructiveHint: false
Only reads 6Show 6 read-only tools
  • get_positionsRead a wallet's open/closed Spiral leverage positions from chain state (read-only).No findings

    Why it is in this group

    • The name "get_positions" says "get": a word for reading.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • title: Get Positions
    • readOnlyHint: true
  • get_pricesCurrent USD prices of every loan and collateral token the chain's strategies use (token address -> USD), including equity-vault stocks.Reads private dataNo findings

    Why it is in this group

    • The name "get_prices" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "vault": it reads secrets.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Prices
    • readOnlyHint: true
  • get_strategyGet one eligible strategy's full raw facts by its Morpho market id.No findings

    Why it is in this group

    • The name "get_strategy" says "get": a word for reading.
    Description, as the server wrote it
    Get one eligible strategy's full raw facts by its Morpho market id.

    Annotations the server declares

    • title: Get Strategy
    • readOnlyHint: true
  • list_strategiesList eligible Spiral strategies on a chain with raw risk facts (collateral/borrow APY, leverage ladder, oracle type, exit liquidity, LTVs, curator).No findings

    Why it is in this group

    • The name "list_strategies" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List Strategies
    • readOnlyHint: true
  • simulate_equity_depositPreview depositing USDG into a stock + yield equity vault — deterministic, read-only, no wallet.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "preview": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "preview" and "vault": it reads secrets.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Simulate Equity Vault Deposit
    • readOnlyHint: true
  • simulate_leveragePreview opening a leveraged position — deterministic, read-only, no wallet needed.No findings

    Why it is in this group

    • The description's first verb is "preview": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Simulate Leverage
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.spiralstake.xyz/mcp: tools/list returned 10 tools to an anonymous client, including build_leverage_tx (write), build_manage_tx (write), build_equity_deposit_tx (write), build_equity_exit_tx (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http leverage https://api.spiralstake.xyz/mcp
claude mcp add --transport http leverage https://api.spiralstake.xyz/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__leverage__list_strategies",
      "mcp__leverage__get_strategy",
      "mcp__leverage__get_prices",
      "mcp__leverage__simulate_leverage",
      "mcp__leverage__get_positions",
      "mcp__leverage__simulate_equity_deposit"
    ],
    "ask": [
      "mcp__leverage__build_leverage_tx",
      "mcp__leverage__build_manage_tx",
      "mcp__leverage__build_equity_deposit_tx",
      "mcp__leverage__build_equity_exit_tx"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as leverage. Review it before you use it.

Capability tags behind 2 rules
  • mcp__leverage__get_prices private-data
  • mcp__leverage__simulate_equity_deposit private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/xyz.spiralstake/leverage/verify?hash=1cf693341b2c2dc971c36ef187ab6d80a7f0b98cf837c9395301dc49b7facf55" | jq -e '.changed == false'

Pinned hash 1cf693341b2c, from Nov 18, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/xyz.spiralstake/leverage/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for xyz.spiralstake/leverage
[![Anlyon Radar](https://radar.anlyon.com/badge/xyz.spiralstake/leverage.svg)](https://radar.anlyon.com/servers/xyz.spiralstake/leverage)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:55 UTC.

leverage MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the leverage MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the leverage MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the leverage MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the leverage MCP server have?

10 tools: 4 write, 6 read. build_leverage_tx, build_manage_tx, build_equity_deposit_tx, build_equity_exit_tx, list_strategies, get_strategy, get_prices, simulate_leverage and 2 more.

Does the leverage MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the leverage MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the leverage MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.