Canton Venues
REMOTE · CANTONVENUES.COM
Live Canton Network DEX data: prices, best execution across venues, exit cost, premiums. No key.
Available components
Last scanned (2 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1960 tokens (~163/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +11
- Authorization: unverified → partial ▲ security
- Schema quality: 126 → 163 ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.1 functional
- “alerts” reworded the description of “limit” cosmetic
- “check_trade” reworded the description of “amount_in” cosmetic
- “check_trade” reworded the description of “amount_out” cosmetic
- “check_trade” reworded the description of “buy” cosmetic
- “check_trade” reworded the description of “sell” cosmetic
- “check_trade” reworded the description of “time” cosmetic
- “check_trade” reworded the description of “venue” cosmetic
- “exit_cost” reworded the description of “amount_usd” cosmetic
- “exit_cost” reworded the description of “symbol” cosmetic
- “list_tokens” reworded the description of “limit” cosmetic
- “list_tokens” reworded the description of “sort_by” cosmetic
- “perps” reworded the description of “base” cosmetic
- “pools” reworded the description of “limit” cosmetic
- “pools” reworded the description of “sort_by” cosmetic
- “premiums” reworded the description of “kind” cosmetic
- “quote” reworded the description of “amount” cosmetic
- “quote” reworded the description of “amount_usd” cosmetic
- “quote” reworded the description of “buy” cosmetic
- “quote” reworded the description of “sell” cosmetic
- “spreads” reworded the description of “limit” cosmetic
- “token” reworded the description of “symbol” cosmetic
- 2 Nov 26 59
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 5 Nov 2026 · Probed https://cantonvenues.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cantonvenues.com | CN=YE2,O=Let's Encrypt,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 67d78ebd11bbdb13ac4d45182d6f377b482 |
| SANs: cantonvenues.com, www.cantonvenues.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 cantonvenues.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cantonvenues.com. | 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://cantonvenues.com/mcp | Verified | 200 | |
| http (plaintext) | http://cantonvenues.com/mcp | HTTPS enforced | 301 | https://cantonvenues.com/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 →
alerts Recent alerts ~65
Alerts fired on Canton DEXes: stablecoin peg breaks, premiums over 1%, hourly moves over 5%, and spreads that clear their costs. Newest last.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many of the latest alerts to return, 1 to 300 |
No output schema declared.
No examples provided.
check_trade Check a trade against every Canton venue at that time ~332
Was a trade well executed? Give the token sold and bought, the amount sold, the amount received, the time (ISO such as 2026-10-27T18:05:00Z, or unix seconds) and optionally the venue. The trade is priced again on every venue from the pool reserves and order books read at the five-minute ticks either side of it (archive since 27 Oct 2026), by the same code as quote(), after network fees. Returns the venue that returned the most, how far the trade fell short of it in basis points (at the reading least favourable to that), and with venue given, how much of the gap was the choice of venue and how much the fill itself. Nothing is executed or stored.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_in | number | yes | How much of the sold token went in, in its own units |
| amount_out | number | yes | How much of the bought token came back, in its own units |
| buy | string | yes | Symbol of the token bought, e.g. USDCx |
| sell | string | yes | Symbol of the token sold, e.g. CC |
| time | string | yes | When the trade ran: ISO 8601 such as 2026-10-27T18:05:00Z, or unix seconds; the archive starts 27 Oct 2026 21:01 UTC |
| venue | – | – | Optional: the venue it ran on, e.g. cantex, tradecraft, oneswap, temple, rocky or poolparty |
No output schema declared.
No examples provided.
exit_cost Exit cost: what selling a token for dollars nets ~248
What selling a token for dollars (USDCx) nets on Canton, as a share of its value at our price: a ladder from $1K to $1M per venue and at the best one (with across_venues when selling the token for CC on one venue and that CC for dollars on another keeps more), the largest sale each venue (and all of them together) takes within 1%, 2% and 5%, what limited each (the cost, or the end of a venue's visible order book), and the worst share at $10K and $50K since the record began. For lending, vault and risk tools: what collateral sells for on Canton, not only what it is quoted at. With amount_usd, also that exact sale priced now on every venue (as quote() would).
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | – | – | Optional: one sale of this size in US dollars, priced now on every venue |
| symbol | string | yes | Token symbol as Canton DEXes name it, e.g. CC (Canton Coin), CBTC, USDCx; list_tokens() gives every symbol |
No output schema declared.
No examples provided.
list_tokens List Canton DEX tokens ~116
Every token on Canton DEXes with price, 24h/7d change, liquidity and volume. sort_by: liquidity, volume, change_24h, change_7d or premium.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many tokens to return, 1 to 100 |
| sort_by | string | – | Order of the list, largest first: liquidity (USD), volume (24h USD), change_24h, change_7d, or premium (largest gap to the outside price, either sign) |
No output schema declared.
No examples provided.
market_overview Canton DEX market overview ~52
Canton DEX market right now: CC price, spot volume per venue we read, Canton's TVL for the day named, top movers, the largest premiums to global prices, and the latest alerts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
perps Perpetual futures ~87
Perp markets on Rocky, Ekiden and Canborsa: price, basis to the outside spot price, funding, spread, open interest and 24h volume where the venue publishes them. base filters by asset, e.g. BTC, ETH or CC.
| Name | Type | Req | Description |
|---|---|---|---|
| base | – | – | Only markets on this asset, e.g. BTC, ETH or CC; leave out for every market |
No output schema declared.
No examples provided.
pools Liquidity pools ~141
CC pools on every AMM (Cantex, Tradecraft, OneSwap, Pool Party) with liquidity, 24h volume where the venue publishes it, fee and LP fee APR from the last 24 hours of volume; a pool whose reserves have stood still while its price left the market carries `not_trading_since`. sort_by: tvl, volume or apr.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many pools to return, 1 to 60 |
| sort_by | string | – | Order of the list, largest first: tvl (USD), volume (24h USD) or apr (LP fee APR) |
No output schema declared.
No examples provided.
premiums Canton premium to global prices ~118
How far Canton DEX prices sit from outside markets: CBTC vs BTC, cETH vs ETH, eXAU and eXAG vs gold and silver spot (while the spot market trades), CC vs global CC, and every stablecoin vs $1. kind: all, reference or peg.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | reference: tokens priced against an outside market (CBTC vs BTC, cETH vs ETH, eXAU, eXAG, CC); peg: stablecoins against $1; all: both |
No output schema declared.
No examples provided.
quote Quote a trade on Canton DEXes ~363
Best execution for selling `amount` of token `sell` (or `amount_usd` worth) for token `buy`, on every venue that can make the trade on its own markets in one or two swaps: an AMM pool (Cantex, Tradecraft, OneSwap, Pool Party), an order book (Temple, Rocky), or two of them in a row on the same venue (Temple: CC to USDCx, then USDCx to CBTC; Pool Party: CC to USDC.B, then USDC.B to CBTC). The same comparison as the site's best execution, at any size. Pool fees, book fees and price impact are included; `after_network_fee` also takes off the venue's per-trade network fee on each swap (the fee table, with which fees are measured, documented or assumed, is in `network_fees`). A pool whose reserves have stood still while its price left the market is no market here (`not_trading`). A venue whose route takes an order book that shows more of a token than exists (a side larger than its registry's total supply) carries `book_shows_more_than_exists`: its price, not a size it can fill.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | – | – | How much of the sold token, in its own units. Give this or amount_usd, not both |
| amount_usd | – | – | Size of the sale in US dollars at our price of the sold token. Give this or amount, not both |
| buy | string | yes | Symbol of the token bought, e.g. USDCx |
| sell | string | yes | Symbol of the token sold, e.g. CC |
No output schema declared.
No examples provided.
spreads Cross-venue spreads ~138
Buy-on-one-venue, sell-on-the-other round trips at their best size, after each venue's network fee: `cost_cc` per route, `swap_cost_cc` per venue (Cantex measured, OneSwap and Tradecraft documented, the rest assumed at 1.5 CC). A trip through an order book in dollars (via=usd) also pays the CC/USDCx leg of each pool side. `clears` is true when one nets at least $0.50.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many routes to return, best first, 1 to 50 |
No output schema declared.
No examples provided.
token Token detail ~87
One token: price, changes, liquidity and volume, price on each venue, premium to its outside reference, its pools with fee APR, and hourly USD prices for the last 7 days.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Token symbol as Canton DEXes name it, e.g. CC (Canton Coin), CBTC, USDCx; list_tokens() gives every symbol |
No output schema declared.
No examples provided.
venues Canton venues and coverage ~66
Every Canton trading venue we know of: type, 24h volume, and whether we price it live, see its volume only, or cannot read it (key needed, testnet, no public API). Also the share of Canton spot DEX volume that these prices cover.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Canton Venues MCP server?
Canton Venues is a hosted endpoint at https://cantonvenues.com/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 · cantonvenues.com
claude mcp add --transport http com-cantonvenues-canton-venues 'https://cantonvenues.com/mcp'
What is the Canton Venues MCP server?
Canton Venues is an MCP server listed in the public MCP registry as com.cantonvenues/canton-venues. Live Canton Network DEX data: prices, best execution across venues, exit cost, premiums. No key. This page covers its hosted endpoint (https://cantonvenues.com/mcp).
Is the Canton Venues MCP server safe to use?
Canton Venues scores 71 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 Canton Venues MCP server expose?
Canton Venues exposes 12 tools: market_overview, list_tokens, token, quote, premiums, and 7 more. Their descriptions and schemas cost roughly 1,813 tokens of context every time the server is loaded.
Does the Canton Venues MCP server require authentication?
No. We connected to Canton Venues without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Canton Venues MCP server still maintained?
Canton Venues is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.