io.github.QBT-Labs/openmm-mcp
REMOTE · MCP.OPENMM.IO · 2 COMPONENTS · SCANNED SEP 20
MCP server for OpenMM — exposes market data, account, trading, and strategy tools to AI agents
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1286 tokens (~71/item across 18 items; 15 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.QBT-Labs/openmm-mcp server?
io.github.QBT-Labs/openmm-mcp is a hosted endpoint at https://mcp.openmm.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.openmm.io
claude mcp add --transport http qbt-labs-openmm-mcp 'https://mcp.openmm.io/mcp'
{
"mcpServers": {
"qbt-labs-openmm-mcp": {
"url": "https://mcp.openmm.io/mcp"
}
}
} {
"servers": {
"qbt-labs-openmm-mcp": {
"type": "http",
"url": "https://mcp.openmm.io/mcp"
}
}
} [mcp_servers.qbt-labs-openmm-mcp] url = "https://mcp.openmm.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"qbt-labs-openmm-mcp": {
"type": "remote",
"url": "https://mcp.openmm.io/mcp",
"enabled": true
}
}
} openclaw mcp add qbt-labs-openmm-mcp --url 'https://mcp.openmm.io/mcp' --transport streamable-http
mcp_servers:
qbt-labs-openmm-mcp:
url: "https://mcp.openmm.io/mcp" {
"McpServers": {
"qbt-labs-openmm-mcp": {
"Transport": "http",
"Url": "https://mcp.openmm.io/mcp"
}
}
} assistant mcp add qbt-labs-openmm-mcp -t streamable-http -u 'https://mcp.openmm.io/mcp'
{
"mcpServers": {
"qbt-labs-openmm-mcp": {
"type": "http",
"url": "https://mcp.openmm.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.openmm.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=openmm.io | CN=YE1,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 638d0cd488339570468d52a100496eae2aa |
| SANs: *.openmm.io, openmm.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.openmm.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| openmm.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.openmm.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.openmm.io/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_all_orders ~70
Cancel all open orders for a trading pair on a supported exchange
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | Exchange to query. Supported: mexc, gateio, bitget, kraken |
| symbol | string | yes | Trading pair symbol (e.g., BTC/USDT, INDY/USDT) |
No output schema declared.
No examples provided.
cancel_order ~80
Cancel a specific order by ID on a supported exchange
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | Exchange to query. Supported: mexc, gateio, bitget, kraken |
| orderId | string | yes | The order ID to cancel |
| symbol | string | yes | Trading pair symbol (e.g., BTC/USDT, INDY/USDT) |
No output schema declared.
No examples provided.
create_order ~127
Create a new order (limit or market) on a supported exchange
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Order amount in base currency |
| exchange | string | yes | Exchange to query. Supported: mexc, gateio, bitget, kraken |
| price | number | – | Order price (required for limit orders, ignored for market orders) |
| side | string | yes | Order side: buy or sell |
| symbol | string | yes | Trading pair symbol (e.g., BTC/USDT, INDY/USDT) |
| type | string | yes | Order type: limit or market |
No output schema declared.
No examples provided.
discover_pools ~46
Discover Cardano DEX liquidity pools for a native token via Iris API
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Cardano token symbol (INDY, SNEK, MIN, NIGHT) |
No output schema declared.
No examples provided.
get_balance ~75
Get account balances for all assets (or a specific asset) on a supported exchange
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Optional asset to filter by (e.g., USDT, BTC). Returns all assets if omitted. |
| exchange | string | yes | Exchange to query. Supported: mexc, gateio, bitget, kraken |
No output schema declared.
No examples provided.
get_cardano_price ~55
Get aggregated price for a Cardano native token from DEX liquidity pools (TOKEN/USDT via ADA bridge)
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Cardano token symbol (INDY, SNEK, MIN, NIGHT) |
No output schema declared.
No examples provided.
get_ohlcv ~135
Get OHLCV (candlestick) data for a trading pair
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | Exchange to query. Supported: mexc, gateio, bitget, kraken |
| limit | number | – | Number of results to return (default: 100, max: 500) |
| symbol | string | yes | Trading pair symbol (e.g., BTC/USDT, INDY/USDT) |
| timeframe | string | – | Candlestick timeframe (1m, 5m, 15m, 30m, 1h, 4h, 1d, 1w) |
No output schema declared.
No examples provided.
get_orderbook ~94
Fetch order book depth (bids and asks) for a trading pair
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | Exchange to query. Supported: mexc, gateio, bitget, kraken |
| limit | number | – | Number of results to return (default: 10, max: 100) |
| symbol | string | yes | Trading pair symbol (e.g., BTC/USDT, INDY/USDT) |
No output schema declared.
No examples provided.
get_strategy_status ~75
Get current grid strategy status: open orders, current price, and P&L estimate
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | Exchange to query. Supported: mexc, gateio, bitget, kraken |
| symbol | string | yes | Trading pair symbol (e.g., BTC/USDT, INDY/USDT) |
No output schema declared.
No examples provided.
get_ticker ~75
Get real-time price, bid/ask, spread, and volume for a trading pair
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | Exchange to query. Supported: mexc, gateio, bitget, kraken |
| symbol | string | yes | Trading pair symbol (e.g., BTC/USDT, INDY/USDT) |
No output schema declared.
No examples provided.
get_trades ~87
Get recent trades for a trading pair
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | Exchange to query. Supported: mexc, gateio, bitget, kraken |
| limit | number | – | Number of results to return (default: 20, max: 100) |
| symbol | string | yes | Trading pair symbol (e.g., BTC/USDT, INDY/USDT) |
No output schema declared.
No examples provided.
list_exchanges ~23
List all supported exchanges with their IDs, features, and required credentials
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_orders ~73
List open orders on a supported exchange, optionally filtered by trading pair symbol
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | Exchange to query. Supported: mexc, gateio, bitget, kraken |
| symbol | string | – | Optional trading pair to filter by (e.g., BTC/USDT). Returns all if omitted. |
No output schema declared.
No examples provided.
start_grid_strategy ~182
Calculate and optionally place grid trading orders around the current price
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Preview grid without placing orders (default: true) |
| exchange | string | yes | Exchange to query. Supported: mexc, gateio, bitget, kraken |
| levels | number | – | Grid levels per side (default: 5) |
| orderSize | number | – | Base order size in quote currency (default: 50) |
| sizeModel | string | – | Size model |
| spacing | number | – | Base spacing as decimal (default: 0.02 = 2%) |
| spacingFactor | number | – | Factor for geometric spacing (default: 1.3) |
| spacingModel | string | – | Spacing model |
| symbol | string | yes | Trading pair symbol (e.g., BTC/USDT, INDY/USDT) |
No output schema declared.
No examples provided.
stop_strategy ~72
Cancel all open orders for a trading pair, effectively stopping any running grid strategy
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | Exchange to query. Supported: mexc, gateio, bitget, kraken |
| symbol | string | yes | Trading pair symbol (e.g., BTC/USDT, INDY/USDT) |
No output schema declared.
No examples provided.
What is the io.github.QBT-Labs/openmm-mcp server?
io.github.QBT-Labs/openmm-mcp is listed in the public MCP registry as io.github.QBT-Labs/openmm-mcp. MCP server for OpenMM, exposes market data, account, trading, and strategy tools to AI agents. This page covers its hosted endpoint (https://mcp.openmm.io/mcp).
Is the io.github.QBT-Labs/openmm-mcp server safe to use?
io.github.QBT-Labs/openmm-mcp scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.QBT-Labs/openmm-mcp server expose?
io.github.QBT-Labs/openmm-mcp exposes 15 tools: list_exchanges, get_ticker, get_orderbook, get_trades, get_ohlcv, and 10 more. Their descriptions and schemas cost roughly 1,269 tokens of context every time the server is loaded.
Does the io.github.QBT-Labs/openmm-mcp server require authentication?
No. We connected to io.github.QBT-Labs/openmm-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.QBT-Labs/openmm-mcp server still maintained?
io.github.QBT-Labs/openmm-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.