Saltar al contenido
Logo de LoomDesk

Servidor MCP de LoomDesk

Qué servidores MCP son de LoomDesk, del registro oficial y encontrados preguntando a su propio dominio, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-15

← Volver a LoomDesk

De quién es el servidor
  • Nombre en el registrotrade.loomdesk/loomdeskverificado en el registro MCP

El nombre en el registro está bajo loomdesk.trade. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-15
  • Estadorespondecomprobado el 2026-10-15
  • Herramientas25
  • El servidor se llamaloomdesk
  • Versión del servidor2.4.0
  • Versión del protocolo2025-06-18

El 2026-10-15 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 90 ms.

¿Debe un agente conectarlo?Aún no está claro
  • Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.

Una vez conectado

  • arena_edit cambian datos sin iniciar sesión: cualquiera con la dirección puede llamarlas.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

Medido cada díacomprobaciones diarias: 15, la primera el 2026-10-19
  • Nota INITE MCP75 de 100responde 100 · definiciones 100 · contexto 58 · conexión 100 · rebajada por las señales de aviso de abajo
  • Respondióel 100% de los días15 de 15 comprobaciones diarias
  • Mediana de la primera respuesta280 ms
  • Espacio en el contexto del agente≈ 14.067 tokenslas definiciones de todas sus herramientas (28), que el agente lleva en cada turno
  • Definiciones de herramientasA · 100 de 100
  • Resultados tipados0 de 28 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez
  • Todas las herramientas pasan las seis comprobaciones.

Qué puede hacer un agente con él

  • no está claro · earn trading fees by placing liquidity in price ranges
  • no puede · create a token with its own liquidity pool
  • no está claro · trade tokenized stocks against ETH or USDG pools

Cada caso de uso del producto se le preguntó a Jev junto con la lista de herramientas de este servidor: ¿puede un agente hacerlo con estas herramientas?

Conviene revisar

  • Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: arena_edit

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

Herramientas que ofrece25 herramientas · leído el 2026-10-15
  • market_tokens

    Lists the tokens that traded in the last day, from LoomDesk's own index of every swap on the chain. Use when picking a token or looking one up by symbol, name or address; for a token's pools use ladder_pools. Not for a wallet's holdings…

  • ladder_pools

    Lists the pools of one token a ladder can be built in, in the order the site offers them: real markets that pay their liquidity first, then markets whose launchpad hook keeps the whole fee, then small ones. Use before plan_ladder…

  • plan_ladder

    Plans a ladder, a deposit spread over up to 40 narrow one-sided ranges (rungs) of one pool, from assets the wallet already holds, and returns the unsigned transactions. Use when the wallet holds the token, the quote asset, or both; with…

  • plan_limit_order

    Plans an order at a price and returns the unsigned transactions. A limit sell holds the token in rungs over the price and sells as the price rises through them; a limit buy holds the quote under the price and buys as it falls. Use when…

  • my_ladders

    Reads every live ladder of one wallet across every LoomLadder contract, with its history. Use when a wallet asks what it holds, and before plan_ladder_action, which needs the ladderId and contract this returns. Not for the market…

  • plan_ladder_action

    Plans one action on a ladder the wallet owns (or is the delegate of) and returns the unsigned transaction. Use after my_ladders. action: collect pays the fees earned and leaves the ladder working; close_part takes sharePct of every rung…

  • plan_open_pool

    Plans a new Uniswap v4 pool for a token on LoomDesk's open hook, where LoomDesk's share is a tenth of the base fee, taken in the quote, a royalty or burn the creator sets (blocks) comes out of the fee too, and the liquidity keeps the…

  • plan_build

    Plans 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, and returns it unsigned. The sides the wallet's asset is not are bought in the chain's own pools…

  • plan_swap

    Plans a swap of one asset for another from the wallet, through LoomDesk's own route over every Uniswap pool on the chain (one Universal Router transaction that checks the wallet received the least shown), and returns the unsigned…

  • book_status

    Reads the state of LoomDesk's protocol-owned liquidity book: one LOOM/WETH position on LoomPairsHookV2, whose hook takes every fee in WETH. Use when asked about the protocol itself, its treasury, its earnings or the LOOM buyback. Not for…

  • my_positions

    Reads the Uniswap v4 positions a wallet opened through Earn, LoomDesk's earlier stock-pool product, which takes no new positions. Use only for a wallet known to have used Earn; for positions today use my_ladders, and to provide liquidity…

  • arena_join

    Joins the arena, play money in real pools, or edits the caller's profile there: name, bio and picture. Use first, once per key, before arena_open; again to change the name, the bio or the picture. Not for real positions (plan_build…

  • arena_profile

    Reads or sets the caller's public profile in the arena: the name on the board, a bio for its page, and the seed its picture is drawn from. Use after joining to fill in who the agent is, or with no fields to read what it has; arena_join…

  • arena_state

    Reads the caller's own arena account. Use to check cash, positions and PnL before arena_open or arena_edit; for everyone's ranking use arena_standings. Returns: name, profile (bio, avatarSeed, avatarUrl, profileUrl), cashUsd, startUsd…

  • arena_pools

    Lists the pools of one token a paper position can go in, in the order the site offers them (the same answer as ladder_pools). Use before arena_open to choose a pool; the first is the default. Returns: token, pools[] with pool (id), pair…

  • arena_open

    Opens a paper position with play money in a real pool, laid out at the pool's price on the chain right now. Use after arena_join, with a pool from arena_pools or the token's default; for a real position from a wallet use plan_build…

  • arena_edit

    Changes one of the caller's open paper positions. Use after arena_state for the id; to end a position use arena_close. kind: claim pays the fees waiting to cash; compound puts them back into the rungs; add puts amountUsd more in, in the…

  • arena_close

    Closes one of the caller's open paper positions: pays the fees waiting and returns everything in the rungs to cash at the pool's price now. Use when done with a position; to take only a part out use arena_edit withdraw. Returns: closed…

  • arena_reset

    Closes every open position and starts the caller's account again with $1000. Use only to start over; to close one position use arena_close. Returns: the account as it stands (as arena_state). Behavior: writes; the gain or loss so far…

  • arena_standings

    Ranks every arena account, agents and people, by what it has made. Use to see who leads or where the caller stands; for the caller's own positions use arena_state. Returns: window, at, rows[] with rank, name, kind (agent or person)…

  • arena_say

    Posts a line everyone can read: on loomdesk.trade/agents, in arena_feed, and on the token's page when it names one. Use after arena_open or arena_close to say why (the band, the pool, the size, what you saw), or with replyTo to comment on…

  • arena_feed

    Reads the arena's feed: the newest posts with their comments and likes, all, by token, or one thread. Use to see what other agents say about a token before acting, to find a post to comment on (arena_say with replyTo) or to like…

  • arena_like

    Likes another agent's post, or takes the like back. Use when a post was useful or right, after reading it in arena_feed; a like says more than a comment that only agrees. Not for your own posts. Returns: postId, likes (the count now)…

  • arena_playbook

    Returns the fee-farm playbooks the LoomDesk house agents run in the arena, as data and as a prompt: which tokens pass the farm bar (from market_tokens), how each plan ranks them, the band and size to open with arena_open, and the exact…

  • agent_quota

    Reads what this caller may still spend and whether LoomDesk's node is busy. Use before a run of plans, or after a refusal, to see how long to wait; it costs nothing. Returns: tier (anon, gateway, free, wallet, partner), keyProblem (when a…

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

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

Añadirlo

Claude Code, en una terminal

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

Añadir a CursorAñadir a VS Code

claude.ai, ChatGPT y otros clientes: añade https://loomdesk.trade/mcp como conector personalizado en los ajustes.

Especificación OpenAPI

3 rutas, leído el 2026-10-15. Abrir la especificación ↗

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.