Omnia Exchange
REMOTE · API.{ENVIRONMENT}.OMNIAEXCHANGE.COM
Omnia Exchange is the institutional liquidity and execution infrastructure layer powered by LMAX
Available components
Last scanned (13 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Finance and Payments
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 259 tokens (~129/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.2.0 → 2.0.5 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 79
First indexed and scored.
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 6 Nov 2026 · Probed https://api.production.omniaexchange.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.production.omniaexchange.com | CN=YE2,O=Let's Encrypt,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5aa4bb7523775275b47535a854f9fd8240d |
| SANs: *.production.omniaexchange.com, production.omniaexchange.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 api.production.omniaexchange.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| omniaexchange.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 400 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.production.omniaexchange.com/.well-known/oauth-protected-resource", scope="account_information account_maintenance trading market_data rfq impersonate hide_custodian_v1_addresses"
Bearer resource_metadata="https://api.production.omniaexchange.com/.well-known/oauth-protected-resource", scope="account_information account_maintenance trading market_data rfq impersonate hide_custodian_v1_addresses"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://api.production.omniaexchange.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.production.omniaexchange.com |
| Authorisation server | https://api.production.omniaexchange.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.production.omniaexchange.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.production.omniaexchange.com/api/mcp | HTTPS enforced | 301 | https://api.production.omniaexchange.com/api/mcp |
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 →
market.get_assets List Assets ~57
List available assets and their details (symbol, name, decimals, chain) for a given source
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | Asset source: OFFCHAIN, ETHEREUM, OPTIMISM, POLYGON, LINEA, etc. |
No output schema declared.
No examples provided.
market.get_price Get Price ~66
Get the current indicative price for a trading pair
| Name | Type | Req | Description |
|---|---|---|---|
| buyingAsset | string | yes | Asset being bought (e.g. USDC) |
| sellingAsset | string | yes | Asset being sold (e.g. ETH) |
| source | string | – | Trading source (defaults to OFFCHAIN) |
No output schema declared.
No examples provided.
How do I install the Omnia Exchange MCP server?
Omnia Exchange is a hosted endpoint at https://api.{environment}.omniaexchange.com/api/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 · api.{environment}.omniaexchange.com
claude mcp add --transport http com-lmax-omnia-exchange 'https://api.{environment}.omniaexchange.com/api/mcp'
What is the Omnia Exchange MCP server?
Omnia Exchange is an MCP server listed in the public MCP registry as com.lmax/omnia-exchange. Omnia Exchange is the institutional liquidity and execution infrastructure layer powered by LMAX. This page covers its hosted endpoint (https://api.{environment}.omniaexchange.com/api/mcp).
Is the Omnia Exchange MCP server safe to use?
Omnia Exchange scores 83 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 Omnia Exchange MCP server expose?
Omnia Exchange exposes 2 tools: market.get_assets, market.get_price. Their descriptions and schemas cost roughly 123 tokens of context every time the server is loaded.
Does the Omnia Exchange MCP server require authentication?
Yes. Omnia Exchange asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Omnia Exchange MCP server still maintained?
Omnia Exchange is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Omnia Exchange MCP server?
VerifyMCP ran 13 checks on Omnia Exchange, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.