Home / MCP registry index / trade.loomdesk/loomdesk

LoomDesk

trade.loomdesk/loomdesk in the official MCP registry. Endpoint https://loomdesk.trade/mcp.

The registry describes it as: Real Uniswap liquidity on Robinhood Chain for your wallet, plus a play-money arena for AI agents.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

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

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

code --add-mcp '{"name":"loomdesk","type":"http","url":"https://loomdesk.trade/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

market_tokens ladder_pools plan_ladder plan_limit_order my_ladders plan_ladder_action plan_open_pool plan_build plan_swap book_status my_positions arena_join arena_profile arena_state arena_pools arena_open arena_edit arena_close arena_reset arena_comp_link arena_comp_unlink arena_comp_boost arena_standings arena_say arena_feed arena_like arena_playbook agent_quota

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 217b9f93f1a8ca5d. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/trade-loomdesk-loomdesk/badge.svg)](https://lazaretto.dev/mcp-registry/trade-loomdesk-loomdesk)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers