# trade.loomdesk/loomdesk (remote · loomdesk.trade)

Tokenized stock pools on Robinhood Chain: where liquidity earns, and the transactions to provide it.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `loomdesk.trade`: 70/100 (this document), [markdown](https://verifymcp.io/servers/trade-loomdesk-loomdesk/loomdesk.md), [page](https://verifymcp.io/servers/trade-loomdesk-loomdesk/loomdesk)

## Channel facts

- Endpoint: `https://loomdesk.trade/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3096 tokens (~221/item across 14 items; 13 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 80/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 39% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the trade.loomdesk/loomdesk MCP server?

trade.loomdesk/loomdesk is a hosted endpoint at https://loomdesk.trade/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.

### Claude

```bash
claude mcp add --transport http trade-loomdesk-loomdesk 'https://loomdesk.trade/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "trade-loomdesk-loomdesk": {
      "url": "https://loomdesk.trade/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "trade-loomdesk-loomdesk": {
      "type": "http",
      "url": "https://loomdesk.trade/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.trade-loomdesk-loomdesk]
url = "https://loomdesk.trade/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "trade-loomdesk-loomdesk": {
      "type": "remote",
      "url": "https://loomdesk.trade/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add trade-loomdesk-loomdesk --url 'https://loomdesk.trade/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  trade-loomdesk-loomdesk:
    url: "https://loomdesk.trade/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "trade-loomdesk-loomdesk": {
      "Transport": "http",
      "Url": "https://loomdesk.trade/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add trade-loomdesk-loomdesk -t streamable-http -u 'https://loomdesk.trade/mcp'
```

### Other

```json
{
  "mcpServers": {
    "trade-loomdesk-loomdesk": {
      "type": "http",
      "url": "https://loomdesk.trade/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-23 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “plan_ladder” rewrote its description, which is the text the model reads
- [security] Tool “plan_open_pool” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 181 → 221
- [functional improvement] Tool coverage: 32% → 39%
- [functional] New tool “plan_build”
- [functional] New tool “plan_swap”
- [cosmetic] “ladder_pools” added an optional parameter “quote”
- [cosmetic] “plan_ladder” added an optional parameter “copyOf”
- [cosmetic] “plan_ladder” added an optional parameter “newPool”
- [cosmetic] “plan_ladder” added an optional parameter “referrer”
- [cosmetic] “plan_open_pool” reworded the description of “feePct”
- [cosmetic] “plan_open_pool” reworded the description of “quote”

### 2026-09-22 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “plan_ladder” rewrote its description, which is the text the model reads

### 2026-09-21 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 66, −2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Tool coverage: 78% → 32%
- [functional regression] Schema quality: pass → fail
- [functional] Server version: 1.0.0 → 2.0.0
- [functional] New tool “ladder_pools”
- [functional] New tool “market_tokens”
- [functional] New tool “my_ladders”
- [functional] New tool “plan_ladder”
- [functional] New tool “plan_ladder_action”
- [functional] New tool “plan_open_pool”

## MCP tools (13)

### `list_pools` (~164 tokens)

List stock/USDG pools

Tokenized stock pools on Robinhood Chain with what a dollar of liquidity earned in them (weekly rate at ±5/10/15/25% ranges), how much of those fees the pool kept after arbitrage (keep), depth, and 24h flow. LoomDesk's own pools are marked own: true; those are the pools Earn opens positions in, and the ones a tenth of whose swap fees pay the LoomDesk book. Rates are measurements of the past week, not forecasts.

Input parameters:

- `limit` (integer)
- `min_depth_usdg` (number): Skip pools shallower than this.
- `own_only` (boolean): Only LoomDesk's own pools (default). false lists every stock pool on the chain.
- `sort` (string)

### `get_pool` (~69 tokens)

One pool in full

Everything list_pools knows about one pool plus its v4 pool key, by symbol (LoomDesk's own pool of that stock if there is one, else the deepest) or by pool id.

Input parameters:

- `pool` (string, required): A stock symbol such as META, or a pool id / address

### `quote_position` (~194 tokens)

Quote a position and build the transactions that open it

For an amount of USDG and a range around the current price in one of LoomDesk's own pools: the 1% fee to open, the stock the desk would buy, the ticks, what the position would have earned per week at the pool's measured rate, and the two transactions (USDG approve, EarnDeskV4.open) that open it, minted to the sender's wallet. Nothing is sent: the caller signs and sends them from its own wallet within 20 minutes. Keep a deposit under maxSensibleDepositUsdg: in a shallow pool a larger buy of the stock side moves the price against you.

Input parameters:

- `pool` (string, required): Symbol or pool id of a LoomDesk pool
- `range_pct` (number): Half-width of the range around the current price, in percent
- `usdg` (number, required): USDG to put in, fee included, e.g. 250

### `book_status` (~43 tokens)

The LoomDesk book

The protocol-owned liquidity book: value, positions, fees collected, earnings waiting for the daily 18:00 UTC payout, and what has been paid to LOOM holders.

### `my_positions` (~47 tokens)

A wallet's Earn positions

The Uniswap v4 positions a wallet opened through LoomDesk Earn: pool, range, whether in range, value and uncollected fees.

Input parameters:

- `address` (string, required): The wallet address

### `market_tokens` (~152 tokens)

What trades on Robinhood Chain

Every token that traded in the last day, from LoomDesk's own index of every swap on the chain: price, market cap, 24h volume, fees, trades, depth, age, tier (established / new / untested) and keep (the share of its fees the busiest pool kept after the price moved). Flagged tokens (a stranger cannot sell them, or they tax transfers) are left out. `query` searches by symbol, name or address. `leadersWindowSeconds` instead returns the most traded and highest volume tokens over that window (300 to 604800).

Input parameters:

- `leadersWindowSeconds` (integer)
- `limit` (integer)
- `query` (string)

### `ladder_pools` (~143 tokens)

The pools of a token a ladder can be built in

For one token: the pools a ladder can go in, in the order the site offers them (real markets that pay their liquidity first; then real markets whose launchpad hook keeps the whole fee, where a ladder is only a grid of orders; then small ones). Each with swap fee, whether it pays liquidity, depth, 24h volume and fees, and fees as a share of liquidity per week. The first is the default.

Input parameters:

- `quote` (string): ETH, USDG or an address: the pair asked about; the answer then says whether that exact pair has a pool, or that plan_build opens one
- `token` (string, required)

### `plan_ladder` (~745 tokens)

Plan a ladder and get the transactions to sign

For a wallet that already holds the assets it brings; from ETH or USDG, plan_build does the whole thing in one transaction. A ladder is one deposit spread over up to 40 narrow one-sided ranges ('rungs') of a Uniswap v3 or v4 pool: rungs under the price hold the quote asset (ETH, WETH, USDG or LOOM) and buy the token as it falls, rungs over the price hold the token and sell it as it rises, and rungs the price trades through earn the pool's swap fee. Give the band as percent from the current price (lowPct negative for under the price), the amounts as decimal strings, and the owner wallet. With one asset only, `split: true` swaps part of it for the other in the same pool and builds the whole band in one transaction (the minimum out comes from the chain's quoter, hook taxes included). Returns the unsigned transactions (approvals if needed, then the open or the zap) laid out from the pool's price on the chain right now. You sign and send them from the owner wallet; nothing is signed or sent here. Fees: 0.25% of what goes in, taken out of the rungs as they are minted (0.1% of it to `referrer` when given, 0.1% to the owner of the ladder `copyOf` names while it is open in the same pair); then 5% of the trading fees the ladder earns and 5% of any gain on the liquidity when it is taken out (nothing from a loss), or 5% of the ladder's value when the NFTs are taken out instead; 3.5% for an owner holding 100,000 LOOM. Every cut is paid as USDG, with a slice of the token sold in the same pool when the money side is short.

Input parameters:

- `amountQuote` (string)
- `amountToken` (string)
- `copyOf` (string): The id of a ladder on the current contract this one copies: its owner is paid 0.1% while it is open in the same pair.
- `fullRange` (boolean): One position across every price instead of a band of rungs. Never out of range and needs no watching; very little of the money sits at the price, so it earns the least per dollar. Needs both amounts,…
- `highPct` (number, required)
- `lowPct` (number, required)
- `newPool` (object): From plan_open_pool's `then`, for a pool being opened in the same plan: the ladder is laid out against its key and opening price. No split in it (it is empty): both amounts, or one for a one-sided la…
- `owner` (string, required)
- `payWithEth` (boolean): For a pool quoted in WETH: pay in plain ETH, wrapped inside the same transaction, with nothing to approve. Default: whenever the wallet holds less WETH than amountQuote.
- `pool` (string): A pool from ladder_pools; the default pool when left out
- `referrer` (string): The wallet that referred the owner: paid 0.1% of what goes in, out of the opening fee, and kept by the contract from the owner's first ladder on.
- `rungs` (integer)
- `shape` (string)
- `slippagePct` (number)
- `split` (boolean)
- `token` (string, required)

### `my_ladders` (~93 tokens)

A wallet's ladders and what it has done

Every live ladder of a wallet (on the current LoomLadder and earlier ones): pair, rungs with what each holds and which side of the price it is on, value, fees waiting (after LoomDesk's share), fees already collected, PnL against simply holding what went in, and the wallet's history of opens, collects, partial withdraws and closes.

Input parameters:

- `address` (string, required)

### `plan_ladder_action` (~184 tokens)

Collect, partly withdraw, close or take out a ladder

The unsigned transaction for one of a ladder's exits. collect: pays the fees earned and leaves the ladder working. close_part: takes sharePct of every rung out, the rest keeps working. close: pays the fees and returns everything. take_nfts: hands the Uniswap position NFTs to the owner; it always works, even when new ladders are paused. close and close_part are simulated first and carry minimums from slippagePct.

Input parameters:

- `action` (string, required)
- `contract` (string): The LoomLadder the ladder lives in, from my_ladders; the current one when left out
- `ladderId` (string, required)
- `owner` (string, required)
- `sharePct` (number)
- `slippagePct` (number)
- `to` (string): Where the proceeds go; the owner when left out

### `plan_open_pool` (~314 tokens)

Open a pool that pays its liquidity

When a token has no pool against the quote wanted (ladder_pools shows none, or none that pays liquidity): plan a new Uniswap v4 pool for it on LoomDesk's open hook, with a flat 1% or 3% swap fee: nine tenths to liquidity providers, one tenth to the LoomDesk book. The quote can be ETH, USDG, a tokenized stock, LOOM, or any token with a real exit (2,000 USDG of liquidity on the chain and a route to USDG): LOOM/PONS, a memecoin against a memecoin. One-off cost about a dollar (1 USDG or 0.0004 ETH), paid by the owner. It opens at the price of the token's existing market. Expect its flow to be mostly arbitrage plus what routers send; a new pool starts with neither. The pool holds nothing until a ladder is built in it: the result's `then` carries the pool id and key for plan_ladder (with newPool), so the pool and the ladder can be planned together and signed in order.

Input parameters:

- `feePct` (integer, required): the pool's swap fee in percent: 1, 2, 3, 4 or 5
- `owner` (string, required)
- `quote` (required): "ETH", "USDG", or the address of the quote token: a tokenized stock, LOOM, or any token with an exit
- `token` (string, required)

### `plan_build` (~320 tokens)

One transaction from ETH or USDG to a ladder, the pool opened on the way

One transaction (two when paying in USDG: its approval first) from ETH or USDG to a ladder in a v4 pool of the token against the quote (ETH, USDG, LOOM, a stock, a memecoin with an exit). The pool is opened on LoomDesk's hook inside the same transaction when the pair has none (feePct 1 to 5, about a dollar); the sides the wallet's asset is not are bought through Nordstern inside it, split by the band; the pool's fee is paid from it; the ladder is built for the owner; leftovers come back. Prefer it over plan_swap + plan_open_pool + plan_ladder whenever the caller pays in ETH or USDG.

Input parameters:

- `amount` (string, required)
- `copyOf` (string)
- `feePct` (integer)
- `fullRange` (boolean)
- `highPct` (number)
- `lowPct` (number): needed unless fullRange
- `owner` (string, required)
- `payIn` (string, required)
- `pool` (string): A v4 pool of the token to build in, by id from ladder_pools: any pool, on the hook or not; the quote is then that pool's
- `quote` (string, required): ETH, USDG, or the quote token's address
- `referrer` (string)
- `rungs` (integer)
- `shape` (string)
- `slippagePct` (number)
- `token` (string, required)

### `plan_swap` (~156 tokens)

Buy a side a plan needs, through Nordstern

The unsigned transactions for a swap on the chain through Nordstern's aggregator (an approval of the router when paying with a token, then the route), with what it returns and the least it may. For a pair the caller wants but only holds ETH or USDG for: one plan_swap per missing side, then plan_ladder with to.atLeast as that side's amount. Nothing is signed here.

Input parameters:

- `amount` (string, required): how much of `from`, as a decimal string
- `from` (string, required): ETH, USDG, a token symbol or address
- `owner` (string, required)
- `slippagePct` (number)
- `to` (string, required): ETH, USDG, a token symbol or address

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/trade-loomdesk-loomdesk/loomdesk#diagnostics

## Score history

- 2026-09-28: 70
- 2026-09-27: 69
- 2026-09-26: 69
- 2026-09-25: 68
- 2026-09-24: 68
- 2026-09-23: 67
- 2026-09-22: 67
- 2026-09-21: 67
- 2026-09-20: 66
- 2026-09-19: 68
- 2026-09-18: 68

## Common questions

### What is the trade.loomdesk/loomdesk MCP server?

trade.loomdesk/loomdesk is an MCP server listed in the public MCP registry as trade.loomdesk/loomdesk. Tokenized stock pools on Robinhood Chain: where liquidity earns, and the transactions to provide it. This page covers its hosted endpoint (https://loomdesk.trade/mcp).

### Is the trade.loomdesk/loomdesk MCP server safe to use?

trade.loomdesk/loomdesk scores 70 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 trade.loomdesk/loomdesk MCP server expose?

trade.loomdesk/loomdesk exposes 13 tools: list_pools, get_pool, quote_position, book_status, my_positions, and 8 more. Their descriptions and schemas cost roughly 2,624 tokens of context every time the server is loaded.

### Does the trade.loomdesk/loomdesk MCP server require authentication?

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

### Is the trade.loomdesk/loomdesk MCP server still maintained?

trade.loomdesk/loomdesk is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://loomdesk.trade/mcp
- Website: https://loomdesk.trade/
- Changelog RSS feed: https://verifymcp.io/servers/trade-loomdesk-loomdesk/loomdesk.xml
- Changelog JSON feed: https://verifymcp.io/servers/trade-loomdesk-loomdesk/loomdesk.json
- HTML version of this page: https://verifymcp.io/servers/trade-loomdesk-loomdesk/loomdesk