
Openmm Mcp
io.github.adacapo21Published by GitHub account adacapo21v1.0.5Updated Oct 24, 2026
AI-native crypto trading MCP server — market data, orders, grid strategies & DeFi
Overview
OpenMM MCP gives an AI assistant crypto market data, account balances, order placement and grid-strategy tools across several exchanges and Cardano DEXes.
- What you can do
- List supported exchanges and read market data: tickers, order books, recent trades and OHLCV candles
- Check account balances and open orders on a configured exchange
- Place limit or market orders, cancel one order or all orders for a pair
- Query Cardano DEX token prices and discover ADA liquidity pools
- Start, stop and inspect grid trading strategies
- When to use it
- Useful when you want an assistant to monitor crypto markets, check exchange balances and open orders, or place and cancel trades and run grid strategies through natural-language requests, with credentials kept in an encrypted local vault.
- Requirements
- Local process on the user's machine; Node.js 20 or later. Install the npm package and run the setup wizard, then initialize the encrypted vault at ~/.openmm/vault.enc with a password, a wallet and optional exchange keys. Clients connect to a local socket started by the serve command. Alternatively, exchange API keys can be passed directly in the environment block, or the hosted endpoint can be used with pay-per-call USDC payments.
Installation
In SourceWeft
- Open Openmm Mcp in the dashboard and add it to a workspace.
- 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
@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
Local Setup
Prerequisites: Node.js 20 or later.
1. Install and configure
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
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
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:
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 --setupinstead — 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:
The vault strengthens every scenario — nothing sensitive exists in any config file, process environment, or client memory.
Client compatibility
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
Security properties
Payment flow
- Agent calls a tool
- Server returns
402 Payment Requiredwith price openmm servesigns EIP-3009 authorization (gasless — no ETH needed)- Server submits payment on-chain and returns data
Tool Pricing
Available Tools (15)
CLI Reference
Setup & Server
Exchange Credentials
Supported exchanges: mexc, gateio, bitget, kraken, binance, coinbase, okx
Wallet
Spending Policy
Advanced
Example Usage
Check BTC price:
Place an order:
Start grid strategy:
Check Cardano token:
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.sockmode0600— 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 serveprocess via IPC
Development
Resources
- OpenMM SDK — Underlying trading SDK
- x402 Package — Payment integration
- MCP Specification — Model Context Protocol docs
- Base Network — L2 for USDC payments
License
MIT
Hosted deployment
A hosted deployment is available on Fronteir AI.
Source: README.md at commit 7f10368
Tools
0Version history
1- v1.0.5LatestSep 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