Model Context Protocol (MCP) server for freee API integration
Canton Venues is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Live Canton Network DEX data: prices, best execution across venues, exit cost, premiums. No key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http canton-venues-mcp https://cantonvenues.com/mcp
# 2 — ask your agent for something these tools do
# market_overview, list_tokens, token and 9 more
Canton Venues costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http canton-venues-mcp https://cantonvenues.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
Every token on Canton DEXes with price, 24h/7d change, liquidity and volume. sort_by: liquidity, volume, change_24h, change_7d or premium.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sort_by | string | no | — |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
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)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sell | string | yes | — |
| buy | string | yes | — |
| amount | no | — | |
| amount_usd | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
Alerts fired on Canton DEXes: stablecoin peg breaks, premiums over 1%, hourly moves over 5%, and spreads that clear their costs. Newest last.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sort_by | string | no | — |
| limit | integer | no | — |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| base | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
| amount_usd | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sell | string | yes | — |
| buy | string | yes | — |
| amount_in | number | yes | — |
| amount_out | number | yes | — |
| time | string | yes | — |
| venue | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Canton Venues or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| market_overview | no tags | |
| list_tokens | no tags | |
| token | no tags | |
| quote | no tags | |
| premiums | no tags | |
| spreads | no tags | |
| alerts | no tags | |
| pools | no tags | |
| venues | no tags | |
| perps | no tags | |
| exit_cost | no tags | |
| check_trade | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Canton Venues can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.