Openmm Mcp

Created By
QBT-Labs3 months ago
AI-native crypto market making toolkit for Cardano DeFi — 13 tools for iAsset trading, CEX/DEX liquidity management, order book analytics, and automated market making strategies.
Overview

Tools

get_ticker

Get current price ticker and 24h stats for a trading pair on a connected CEX or DEX.

get_orderbook

Fetch the full order book (bids and asks) for a given trading pair.

get_trades

Retrieve recent public trades for a trading pair.

get_balance

Get token/asset balances for a connected exchange account or wallet.

list_orders

List all open orders for a trading pair on a connected exchange.

create_order

Place a new limit or market order on a connected exchange.

cancel_all_orders

Cancel all open orders for a trading pair on a connected exchange.

start_grid_strategy

Start an automated grid market making strategy for a given trading pair with configurable price range and grid levels.

stop_strategy

Stop a running market making strategy.

get_strategy_status

Get the current status, PnL, and fill stats of a running or completed strategy.

get_cardano_price

Fetch the current ADA price and market data from on-chain or aggregated sources.

discover_pools

Discover available DEX liquidity pools for iAsset trading on Cardano DeFi protocols.


Supported exchanges: MEXC, Bitget, Gate.io, Kraken

Server Config

{
  "mcpServers": {
    "openmm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@qbtlabs/openmm-mcp"
      ]
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
QBT-Labs
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago