Spot Advanced Swap Orders

io.github.orbs-networkPublished by GitHub account orbs-networkv2.3.2Updated Oct 24, 2026

Create gasless market, limit, TWAP, stop-loss, take-profit, and delayed-start swap orders.

The publisher's own server: Spot

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

A local MCP server for Spot that lets an assistant create gasless market, limit, TWAP, stop-loss, take-profit and delayed-start swap orders on EVM chains.

What you can do
Create market swap orders at the current price within a slippage limit, and limit orders that fill only when a minimum output can be met. Set up TWAP orders that split a total amount into equal chunks at regular intervals. Define stop-loss and take-profit orders that trigger when the price crosses a threshold. Schedule delayed-start orders for a later eligibility time, with expiration and price conditions constraining each fill.
When to use it
Use it when you want an assistant to help build or schedule non-custodial swap orders on EVM chains, including recurring TWAP execution or conditional stop-loss and take-profit exits, without handing funds to a custodian.
Requirements
Runs as a local process over stdio, installed from the npm package @orbs-network/spot, so a Node.js runtime is needed. No authentication, environment variables or headers are declared. Orders must be signed, and the README points to supported chains and contract addresses.
Before you install
Orders involve real funds and signing; funds stay in the wallet until execution, but signed orders can be filled when conditions are met. Review price conditions, slippage limits and expiration carefully before signing. The README also mentions a hosted MCP endpoint as an alternative, which would send order data to a third party.

Installation

In SourceWeft

  1. Open Spot Advanced Swap Orders in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Spot

Non-custodial market, limit, TWAP, stop-loss, take-profit, and delayed-start orders on EVM chains.

💱 Order Types

  1. Market: Swap at the current price within your slippage limit.
  2. Limit: Swap only when your minimum output can be met.
  3. TWAP: Split a total amount into equal chunks at regular intervals.
  4. Stop-loss: Trigger a swap when the price falls below your threshold.
  5. Take-profit: Trigger a swap when the price rises above your threshold.
  6. Delayed start: Schedule when your order becomes eligible.

⚙️ How It Works

Choose your tokens, total amount, price conditions, and expiration. For recurring orders, set the chunk size and interval. Sign the order; executors fill it when its conditions are met.

Your funds remain in your wallet until execution. Price checks, slippage limits, and expiration constrain each fill.

🌐 Supported Chains

See supported chains and contract addresses.

🚀 Get Started

  1. AI agents: Use the Spot Advanced Swap Orders skill, available on Clawhub, or connect to the hosted MCP endpoint.
  2. Integrators: Follow the API, TypeScript, React, and swap-routing guides.
  3. Support: Report a bug or request a feature.

🔒 Security

Spot's contracts were audited by AstraSec: initial audit and updated audit.

📄 License

MIT.

Source: README.md at commit b4f7a94

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.3.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Spot integrations