trade.loomdesk/loomdesk
REMOTE · LOOMDESK.TRADE · SCANNED SEP 28
Tokenized stock pools on Robinhood Chain: where liquidity earns, and the transactions to provide it.
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 Security63
- 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 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 39% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · loomdesk.trade
claude mcp add --transport http trade-loomdesk-loomdesk 'https://loomdesk.trade/mcp'
{
"mcpServers": {
"trade-loomdesk-loomdesk": {
"url": "https://loomdesk.trade/mcp"
}
}
} {
"servers": {
"trade-loomdesk-loomdesk": {
"type": "http",
"url": "https://loomdesk.trade/mcp"
}
}
} [mcp_servers.trade-loomdesk-loomdesk] url = "https://loomdesk.trade/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"trade-loomdesk-loomdesk": {
"type": "remote",
"url": "https://loomdesk.trade/mcp",
"enabled": true
}
}
} openclaw mcp add trade-loomdesk-loomdesk --url 'https://loomdesk.trade/mcp' --transport streamable-http
mcp_servers:
trade-loomdesk-loomdesk:
url: "https://loomdesk.trade/mcp" {
"McpServers": {
"trade-loomdesk-loomdesk": {
"Transport": "http",
"Url": "https://loomdesk.trade/mcp"
}
}
} assistant mcp add trade-loomdesk-loomdesk -t streamable-http -u 'https://loomdesk.trade/mcp'
{
"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.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +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.
- 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
- 24 Sept 26 +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.
- 23 Sept 26 0
- 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 security
- Schema quality: 181 → 221 ▼ functional
- Tool coverage: 32% → 39% ▲ functional
- New tool “plan_build” functional
- New tool “plan_swap” functional
- “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” cosmetic
- 22 Sept 26 0
- 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
- 21 Sept 26 +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.
- 20 Sept 26 −2
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 78% → 32% ▼ functional
- 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” functional
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 28 Sept 2026 · Probed https://loomdesk.trade/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=loomdesk.trade | CN=YE2,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 58623462e812c626d6eb61d25304cdaf30a |
| SANs: *.loomdesk.trade, loomdesk.trade | ||||||
| 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 insecure
Validation of loomdesk.trade. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| trade. | present | 64969 | 8 | Verified |
| loomdesk.trade. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self'; connect-src 'self' https://*.coinbase.com wss://*.walletlink.org https://*.walletlink.org https://metamask-sdk.api.cx.metamask.io wss://metamask-sdk.api.cx.metamask.io https://mm-sdk-analytics.api.cx.metamask.io; frame-src 'none'; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://loomdesk.trade/mcp | Verified | 200 | |
| http (plaintext) | http://loomdesk.trade/mcp | HTTPS enforced | 308 | https://loomdesk.trade/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 →
book_status The LoomDesk book ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pool One pool in full ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pool | string | yes | A stock symbol such as META, or a pool id / address |
No output schema declared.
No examples provided.
ladder_pools The pools of a token a ladder can be built in ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
list_pools List stock/USDG pools ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
market_tokens What trades on Robinhood Chain ~152
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).
| Name | Type | Req | Description |
|---|---|---|---|
| leadersWindowSeconds | integer | – | – |
| limit | integer | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
my_ladders A wallet's ladders and what it has done ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
my_positions A wallet's Earn positions ~47
The Uniswap v4 positions a wallet opened through LoomDesk Earn: pool, range, whether in range, value and uncollected fees.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The wallet address |
No output schema declared.
No examples provided.
plan_build One transaction from ETH or USDG to a ladder, the pool opened on the way ~320
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| copyOf | string | – | – |
| feePct | integer | – | – |
| fullRange | boolean | – | – |
| highPct | number | – | – |
| lowPct | number | – | needed unless fullRange |
| owner | string | yes | – |
| payIn | string | yes | – |
| 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 | yes | ETH, USDG, or the quote token's address |
| referrer | string | – | – |
| rungs | integer | – | – |
| shape | string | – | – |
| slippagePct | number | – | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
plan_ladder Plan a ladder and get the transactions to sign ~745
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| lowPct | number | yes | – |
| 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 | yes | – |
| 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 | yes | – |
No output schema declared.
No examples provided.
plan_ladder_action Collect, partly withdraw, close or take out a ladder ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| contract | string | – | The LoomLadder the ladder lives in, from my_ladders; the current one when left out |
| ladderId | string | yes | – |
| owner | string | yes | – |
| sharePct | number | – | – |
| slippagePct | number | – | – |
| to | string | – | Where the proceeds go; the owner when left out |
No output schema declared.
No examples provided.
plan_open_pool Open a pool that pays its liquidity ~314
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.
| Name | Type | Req | Description |
|---|---|---|---|
| feePct | integer | yes | the pool's swap fee in percent: 1, 2, 3, 4 or 5 |
| owner | string | yes | – |
| quote | – | yes | "ETH", "USDG", or the address of the quote token: a tokenized stock, LOOM, or any token with an exit |
| token | string | yes | – |
No output schema declared.
No examples provided.
plan_swap Buy a side a plan needs, through Nordstern ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | how much of `from`, as a decimal string |
| from | string | yes | ETH, USDG, a token symbol or address |
| owner | string | yes | – |
| slippagePct | number | – | – |
| to | string | yes | ETH, USDG, a token symbol or address |
No output schema declared.
No examples provided.
quote_position Quote a position and build the transactions that open it ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pool | string | yes | Symbol or pool id of a LoomDesk pool |
| range_pct | number | – | Half-width of the range around the current price, in percent |
| usdg | number | yes | USDG to put in, fee included, e.g. 250 |
No output schema declared.
No examples provided.
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.