@bskts/mcp

The bskts API as tools for Claude, ChatGPT, Cursor and any other MCP client: read tokenized index baskets on Robinhood Chain, check an account, and build buys, sells and orders.

Unsigned only. Build tools return the transactions (approval, then tx) for the user's own wallet to sign. The server holds no key and sends nothing. Built on the official MCP TypeScript SDK and @bskts/sdk.

Tools

All tools are annotated read-only: even the build tools only return data. The rules an agent needs (units, approval order, never send a failed dry run) are in the descriptions and the server instructions.

Local (stdio)

Claude Code:

claude mcp add bskts -e BSKTS_MAX_USD_PER_TRADE=100 -- npx -y @bskts/mcp

Claude Desktop, Cursor and other clients (mcpServers in their config):

{
  "mcpServers": {
    "bskts": {
      "command": "npx",
      "args": ["-y", "@bskts/mcp"],
      "env": { "BSKTS_MAX_USD_PER_TRADE": "100" }
    }
  }
}

Remote (Streamable HTTP)

createBsktsMcpHandler() is a stateless (Request) => Response handler for any fetch-style runtime:

import { createBsktsMcpHandler } from "@bskts/mcp";

const mcp = createBsktsMcpHandler({ policy: { maxUsdPerTrade: 100 } });
export default {
  fetch: (req: Request) =>
    new URL(req.url).pathname === "/mcp" ? mcp(req) : new Response("not found", { status: 404 }),
};

Limits

The user's own guard rails, checked before anything is built (environment variables for the CLI, policy for the handler):

The buy-cost cap applies to market and limit buys through both wallet and delegated tools. A limit's current buy cost is checked when placing the order; its on-chain slippage floor governs the later fill. Sells, exits and cancellations do not require a buy-cost estimate.

MIT

Autonomous account path

Four additional unsigned tools expose delegated accounts:

Create the signing key in your agent host wallet/secure signer; share only its public address. The owner connects that address in Portfolio once, reviews limits and signs. Suggested defaults: 10% available USDG (at least $10) capped $100/day, 0.5% all-in slippage and seven days, fixed dollars until the owner approves a change. A funded bskts account is required; owner/agent ETH is not.

This MCP server stays unsigned. It does not generate/store private keys, grant permissions, sign, submit trades or withdraw. Autonomous execution requires a host signer/submitter; @bskts/sdk provides executeSession and sessionRelayer for that host. Revocation blocks new requests after confirmation; existing orders/schedules require separate cancellation. Reconnect with a fresh key. On a 402 fee quote preserve nonce and trade terms, re-sign only the fee within the host's explicit fee cap. Never automatically replace an ambiguous submission with a new nonce.

Persist the unsigned plan before the host signs or submits it. On restart, reconcile that original nonce and stop while it is unresolved. SDK 0.5.0 hosts can use executeSessionOnce with a durable store and sessionActionState; Node hosts can import fileSessionStore from @bskts/sdk/node. Keep completed records so restarting an operation cannot repeat its trade. MCP continues to return unsigned plans; persistence, signing and reconciliation belong to the host.

Agent keys authorise account trading, including Weekend Cover when it is enabled. Cover spending is counted separately against the same daily limit; underwriting additionally requires the account owner’s allowance. Individual key revocation leaves existing Cover listings open: withdraw them in My cover. The API’s moduleEnabled/coverEnabled fields report the current account setup.

Delegated limit orders

Available since 0.4.2 (the hosted MCP serves it too).

bskts_agent_order builds unsigned session Actions for kind: "limit" (owner, key, ticker, amountUsdg, positive triggerNav, slippageBps, optional expiryDays) and kind: "cancel" (owner, key, orderId). Read the session first, then use bskts_account with its bskts account address to list orders. Creation escrows the whole budget against today's turnover; cancellation returns it to the account without restoring turnover. slippageBps is required for a limit: 50-1000 bps, at most the session's maxSlippageBps and at least the basket's limitMinSlippageBps from bskts_basket (the bskts app uses 300). Expiry cannot exceed the session expiry. The escrow needs at least 50 bps of slippage permission. Revocation leaves existing orders in place. The MCP reconstructs typed data locally and never signs or sends. A host signer should use executeSessionOnce with a durable ID; a placement receipt confirms creation, not a fill.

Since 0.5.0 it also builds kind: "exit" (owner, key, ticker, shares as "max" or walletSharesWei, stopNav and/or tpNav, slippageBps at least the basket's exitMinSlippageBps, optional expiryDays), kind: "cancel-exit" (owner, key, orderId of an exit), and buy-above limits (triggerBelow: false). Every result leads with previewText and preview: the NAV now, each trigger's distance from it, an exit's return against the account's average entry before and after costs, a limit's most per share, each at the trigger (not a bound: after a gap a stop sells lower and a buy-above pays more). Triggers are on NAV (price returns, not net profit): show the preview to the user before anything is signed.