mcpField
O
openmm-mcp

openmm-mcp

Remote
github.com/QBT-LabsFinance3Updated 7w ago
Repository

About openmm-mcp

openmm-mcp is an MCP server for AI agents that need exchange and Cardano DEX data, account access, trading, or grid strategies. It offers local and hosted use, with an encrypted credential vault for local deployments.

Key features

  1. 01Exchange market data tools
  2. 02Account balance and order tools
  3. 03Order placement and cancellation
  4. 04Cardano DEX price and pool discovery
  5. 05Grid strategy controls
  6. 06Encrypted credential vault

Use cases

  1. 01Check exchange prices and order books
  2. 02Review balances and open orders
  3. 03Place or cancel exchange orders
  4. 04Start or inspect a grid strategy

MCP support

Exposes market data, account, trading, Cardano DEX, and strategy tools to MCP clients. Local clients connect through a shared socket; a hosted server is also available.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.openmm.io/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Packages
npm@qbtlabs/openmm-mcp1.0.14

Tools

13
ParameterTypeRequiredDescription
symbolstringYesTrading pair symbol (e.g., BTC/USDT, INDY/USDT)
exchangestringYesExchange to query. Supported: mexc, gateio, bitget, kraken

Details

From the project README

@qbtlabs/openmm-mcp

smithery badge npm version npm downloads License: MIT Ask DeepWiki

📚 Documentation · 🤖 AI Skills Portal · 🔌 API Reference

MCP server for OpenMM — exposes market data, account, trading, and strategy tools to AI agents via any MCP client.

openmm-mcp MCP server

Two Ways to Use

OptionBest ForAPI KeysPayments
Local (npm)Full control, your own keysEncrypted vaultFree
Hosted (mcp.openmm.io)No setup, pay-per-useNot needed for public datax402 USDC

Local Setup

Prerequisites: Node.js 20 or later.

1. Install and configure
npm install -g @qbtlabs/openmm-mcp
openmm-mcp --setup

The setup wizard writes the correct MCP config for your client (Claude Desktop, Claude Code, Cursor, Windsurf). No credentials are stored in config files — only the socket path.

2. Initialize encrypted vault
openmm-init

This creates an encrypted vault at ~/.openmm/vault.enc containing your wallet key and exchange API credentials. You'll set a password, generate (or import) a wallet, and optionally add exchange keys.

3. Start the server
openmm serve

Type your vault password once. The unified socket starts at /tmp/openmm.sock — all MCP clients connect here. No credentials exist in any config file.

Manual configuration

If you prefer to edit config files directly instead of using --setup:

ClientConfig file
Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.json
Claude Code~/.claude.json
Cursor.cursor/mcp.json
Windsurf~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "openmm": {
      "command": "node",
      "args": ["/path/to/openmm-mcp/dist/index.js"],
      "env": {
        "MCP_TRANSPORT": "stdio",
        "OPENMM_SOCKET": "/tmp/openmm.sock",
        "PAYMENT_SERVER": "https://mcp.openmm.io",
        "X402_TESTNET": "true"
      }
    }
  }
}

Replace /path/to/openmm-mcp with the actual install path. For Claude Desktop, use the full path to node (e.g. from which node) to avoid nvm/PATH issues.

Tip: Run openmm-mcp --setup instead — it writes the correct absolute paths automatically.

No API keys. No private keys. No passwords. Just the socket path.

Without vault (quick start)

You can skip the vault and pass API keys directly in the env block:

{
  "mcpServers": {
    "openmm": {
      "command": "npx",
      "args": ["@qbtlabs/openmm-mcp"],
      "env": {
        "MEXC_API_KEY": "your_key",
        "MEXC_SECRET": "your_secret"
      }
    }
  }
}

The vault strengthens every scenario — nothing sensitive exists in any config file, process environment, or client memory.

Client compatibility
ClientWithout vaultWith vault
Claude DesktopAPI keys in envOnly OPENMM_SOCKET
Claude CodeAPI keys in envOnly OPENMM_SOCKET
CursorAPI keys in envOnly OPENMM_SOCKET
WindsurfAPI keys in envOnly OPENMM_SOCKET

All clients connect to the same running openmm serve — one vault, one socket, any client.


Hosted Server with x402 Payments

Connect to mcp.openmm.io — no local installation needed for public data. Pay per tool call with USDC on Base.

How it works
AI Agent (Claude / Cursor / Windsurf)
│  MCP stdio — no keys in config
▼
MCP Client Process
(reads OPENMM_SOCKET — credentials never here)
│  Unix socket /tmp/openmm.sock (mode 0600)
▼
openmm serve — unified vault process
┌──────────────────────────────────┐
│  ~/.openmm/vault.enc             │
│  AES-256-GCM + PBKDF2           │  ← wallet key + exchange keys, one vault
│            │                     │
│  Policy Engine                   │  ← maxPerTx, maxPerDay, allowedChains
│  (checked before key is touched) │
│            │                     │
│  signAndWipe()                   │  ← key used inline, wiped from memory
└──────────────────────────────────┘
│  EIP-3009 signature only
▼
mcp.openmm.io → x402 verification → Base L2 settlement
Security properties
PropertyHow
Keys encrypted at restAES-256-GCM + PBKDF2 in ~/.openmm/vault.enc
Keys never in client memoryMCP process only holds socket path
Keys never in config filesNo API keys, no private keys anywhere in config
Process isolationSigning happens in openmm serve, not in the AI agent process
Policy enforcementSpending limits checked before private key is accessed
Memory safetysignAndWipe() — key used once, goes out of scope immediately
Payment flow
  1. Agent calls a tool
  2. Server returns 402 Payment Required with price
  3. openmm serve signs EIP-3009 authorization (gasless — no ETH needed)
  4. Server submits payment on-chain and returns data
Tool Pricing
CategoryToolsPrice (USDC)
Freelist_exchanges$0.00
Readget_ticker, get_orderbook, get_trades, get_ohlcv, get_balance, list_orders, get_cardano_price, discover_pools, get_strategy_status$0.001
Writecreate_order, cancel_order, cancel_all_orders, start_grid_strategy, stop_strategy$0.01

Available Tools (15)

ToolDescriptionParameters
Market Data
list_exchangesList supported exchanges—
get_tickerReal-time price, bid/ask, spread, volumeexchange, symbol
get_orderbookOrder book depth (bids/asks)exchange, symbol, limit?
get_tradesRecent trades with buy/sell summaryexchange, symbol, limit?
get_ohlcvOHLCV candlestick dataexchange, symbol, timeframe?, limit?
Account
get_balanceAccount balances (all or filtered)exchange, asset?
list_ordersOpen orders (all or by symbol)exchange, symbol?
Trading
create_orderPlace limit or market orderexchange, symbol, type, side, amount, price?
cancel_orderCancel order by IDexchange, symbol, orderId
cancel_all_ordersCancel all orders for a pairexchange, symbol
Cardano DEX
get_cardano_priceAggregated token price from DEXessymbol
discover_poolsDiscover direct ADA pools via Minswap and SundaeSwapsymbol
Strategy
start_grid_strategyStart grid tradingexchange, symbol, lowerPrice, upperPrice, gridLevels?, totalAmount
stop_strategyStop a running strategystrategyId, cancelOrders?
get_strategy_statusGet strategy statusstrategyId

CLI Reference

Setup & Server
CommandDescription
openmm-initCreate vault, generate/import wallet, add exchanges
openmm-init --import <key>Create vault with an existing private key
openmm serveUnlock vault, start unified socket
openmm-statusShow vault, socket, wallet, and exchange status (no password)
Exchange Credentials
CommandDescription
openmm-exchange listList configured exchanges
openmm-exchange add <id>Add exchange credentials
openmm-exchange remove <id>Remove exchange credentials

Supported exchanges: mexc, gateio, bitget, kraken, binance, coinbase, okx

Wallet
CommandDescription
openmm-wallet infoShow wallet address and chain
openmm-wallet setSet wallet credentials
openmm-wallet exportDisplay private key (requires confirmation)
Spending Policy
CommandDescription
openmm-policy showShow current policy
openmm-policy set max-per-tx <amount>Max USDC per transaction
openmm-policy set max-per-day <amount>Max USDC per day
openmm-policy set allowed-chains <chains>Comma-separated chain IDs
openmm-policy resetClear all policy limits
Advanced
CommandDescription
openmm-vault infoShow vault metadata
openmm-vault change-passwordChange vault password
openmm-vault exportExport all credentials (dangerous)
openmm-vault destroyDelete the vault

Example Usage

Check BTC price:

"Get me the BTC/USDT ticker on MEXC"

Place an order:

"Buy 0.1 ETH at $2400 on Kraken"

Start grid strategy:

"Start a grid strategy on MEXC for INDY/USDT between $0.10 and $0.15 with 10 levels and $500 total"

Check Cardano token:

"What's the current price of SNEK on Cardano DEXes?"

Security

  • Vault: AES-256-GCM encrypted at ~/.openmm/vault.enc
  • Password: Interactive terminal only — never in any config file, env var, or CLI flag
  • Socket: /tmp/openmm.sock mode 0600 — the socket is the authentication boundary
  • Policy: Spending limits enforced at the socket before the private key is touched
  • Isolation: Private key never enters any MCP client process memory — signing happens in the openmm serve process via IPC

Development

git clone https://github.com/QBT-Labs/openMM-MCP.git
cd openMM-MCP
npm install
npm run typecheck
npm run lint
npm test
npm run build

Resources

License

MIT

Hosted deployment

A hosted deployment is available on Fronteir AI.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.