xyz.spiralstake/leverage
REMOTE · API.SPIRALSTAKE.XYZ · SCANNED SEP 20
Leveraged-yield router on Morpho. List strategies, simulate, and build UNSIGNED txs.
Available components
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1864 tokens (~266/item across 7 items; 7 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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
claude mcp add --transport http xyz-spiralstake-leverage 'https://api.spiralstake.xyz/mcp'
{
"mcpServers": {
"xyz-spiralstake-leverage": {
"url": "https://api.spiralstake.xyz/mcp"
}
}
} {
"servers": {
"xyz-spiralstake-leverage": {
"type": "http",
"url": "https://api.spiralstake.xyz/mcp"
}
}
} [mcp_servers.xyz-spiralstake-leverage] url = "https://api.spiralstake.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-spiralstake-leverage": {
"type": "remote",
"url": "https://api.spiralstake.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-spiralstake-leverage --url 'https://api.spiralstake.xyz/mcp' --transport streamable-http
mcp_servers:
xyz-spiralstake-leverage:
url: "https://api.spiralstake.xyz/mcp" {
"McpServers": {
"xyz-spiralstake-leverage": {
"Transport": "http",
"Url": "https://api.spiralstake.xyz/mcp"
}
}
} assistant mcp add xyz-spiralstake-leverage -t streamable-http -u 'https://api.spiralstake.xyz/mcp'
{
"mcpServers": {
"xyz-spiralstake-leverage": {
"type": "http",
"url": "https://api.spiralstake.xyz/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 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=YE1,O=Let's Encrypt,C=US | 30 Jul 2026 | 28 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 53cea225294d87a5dbe9f8889bef632a586 |
| SANs: api.spiralstake.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
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 →
build_leverage_tx Build Leverage Transaction ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount of payToken in human units (e.g. '10000' for 10,000 USDC). |
| chainId | integer | – | Chain to target. Supported: 1, 4663. Default: 1. |
| desiredLtv | string | – | Target LTV percent, e.g. '66.67'. Provide this OR leverage. |
| leverage | number | – | Target leverage, e.g. 3. Provide this OR desiredLtv. |
| payToken | string | yes | Address 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. |
| slippage | number | – | Swap slippage as a ratio (0.005 = 0.5%). Default 0.005, capped at 0.01. |
| strategyId | string | yes | Morpho market id of the strategy (from list_strategies / get_strategy). |
| userAddress | string | yes | The wallet address that will sign and send. Approvals and onBehalfOf are built for it. |
No output schema declared.
No examples provided.
build_manage_tx Build Manage Transaction ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What to do to the position. |
| amount | string | – | Human-units amount. Required for add_collateral/remove_collateral/repay/borrow. |
| chainId | integer | – | Chain to target. Supported: 1, 4663. Default: 1. |
| desiredLtv | string | – | increase_leverage: target LTV percent (e.g. '80'). Provide this OR leverage. |
| full | boolean | – | repay only: clear the entire remaining debt. |
| id | integer | yes | On-chain position index, from get_positions (its `id`). |
| leverage | number | – | increase_leverage: target leverage. Provide this OR desiredLtv. |
| payToken | string | – | Token to pay in (add_collateral/repay). Collateral/loan = direct; any other = zapped. ETH = zero address. |
| slippage | number | – | Swap slippage ratio (0.005 = 0.5%). Default 0.005, capped at 0.01. |
| userAddress | string | yes | Wallet that owns the position and will sign. |
No output schema declared.
No examples provided.
get_positions Get Positions ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | – | Chain to target. Supported: 1, 4663. Default: 1. |
| userAddress | string | yes | Wallet address to read positions for. |
No output schema declared.
No examples provided.
get_prices Get Prices ~48
Current USD prices for loan/collateral tokens (token address -> USD).
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | – | Chain to target. Supported: 1, 4663. Default: 1. |
No output schema declared.
No examples provided.
get_strategy Get Strategy ~68
Get one eligible strategy's full raw facts by its Morpho market id.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | – | Chain to target. Supported: 1, 4663. Default: 1. |
| id | string | yes | Morpho market id (0x followed by 64 hex chars). |
No output schema declared.
No examples provided.
list_strategies List Strategies ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by collateral category, e.g. 'stable', 'ETH', 'BTC', 'stable-PT'. |
| chainId | integer | – | Chain to target. Supported: 1, 4663. Default: 1. |
No output schema declared.
No examples provided.
simulate_leverage 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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount of payToken in human units (e.g. '10000' for 10,000 USDC). |
| chainId | integer | – | Chain to target. Supported: 1, 4663. Default: 1. |
| desiredLtv | string | – | Target LTV percent, e.g. '66.67'. Provide this OR leverage. |
| leverage | number | – | Target leverage, e.g. 3. Provide this OR desiredLtv. |
| payToken | string | yes | Address 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. |
| slippage | number | – | Swap slippage as a ratio (0.005 = 0.5%). Default 0.005, capped at 0.01. |
| strategyId | string | yes | Morpho market id of the strategy (from list_strategies / get_strategy). |
No output schema declared.
No examples provided.
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 78 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 7 tools: list_strategies, get_strategy, get_prices, simulate_leverage, build_leverage_tx, and 2 more. Their descriptions and schemas cost roughly 1,415 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.