avee MCP server
A remote Model Context Protocol server over the avee DEX index. Every tool is read-only. No key, no install.
- URL:
https://mcp.preview.avee.tech/mcp(streamable HTTP, stateless; one POST per exchange) - Docs: https://docs.preview.avee.tech
Connect
Claude Code
claude mcp add --transport http avee https://mcp.preview.avee.tech/mcp
claude mcp add --transport http --scope user avee https://mcp.preview.avee.tech/mcp # every project
Cursor: one click with
this install link,
or add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project) the block below.
Claude Desktop and claude.ai: Settings → Connectors → add a custom connector with the URL. VS Code, Windsurf and most other clients take the same JSON block in their MCP configuration:
{ "mcpServers": { "avee": { "type": "http", "url": "https://mcp.preview.avee.tech/mcp" } } }
Check the connection by listing tools: the server advertises its tools and two resources
(avee://chains, avee://reasons).
Pick the right tool
- Name, symbol or ticker →
find_assetfirst. Every pair, token and wallet tool needs an address and a chain. Also call it when an address arrives without a chain. - "Is this safe / what is this token?" →
get_token_brief. One call instead ofget_token+get_pair+get_token_verdict. Read the verdict carefully:okmeans nothing is recorded against the token, not that it is safe;unknownmeans nobody evaluated it. - Lists and rankings →
get_pair_listorget_token_listwithsort_byand filters; useonly_trustable: trueto drop scam-flagged pairs. - Price history →
get_candles; recent trades →get_order_book; a launcher's record →get_deployer_launches; chain or venue rankings →get_leaderboard. - Freshness doubts →
get_latest_blocks. Which chains are served →get_chains.
The full list, with the tools that only some deployments carry and their fallbacks: references/tools.md.
Conventions
chaintakes a name from a fixed enum (robinhood,hyperevm,ton,hyperliquid, …); the enum is wider than what one server serves, soget_chainsis the truth.chain_idis the numeric alternative.- Ranked lists come back highest first; pass
order_by: "asc"for the other end. - Paged tools return
next_cursor; pass it back ascursor. limitis capped at 500. An answer is capped at about 80 kB: an oversized page comes back with"truncated": trueand how many rows were dropped. Narrow the filters or lowerlimitrather than paging blind.- EVM addresses are matched in any case and come back lower-case without
0x. TON, Solana and Hyperliquid addresses are used as given. - Bad arguments fail the call with a message saying what to fix; correct and retry.
Limits
Keyless callers share the same per-address budget as the REST API: 5 tool calls per second, burst
20; each tool call counts as one call, and so does a resource read. Over it, the tool returns a
rate-limit error: wait a few seconds and retry, and do not fan out parallel calls. A key
(X-API-Key header) only raises the budget; nothing in the tool set requires one.
x402 on MCP (when enabled)
When x402 is enabled on the server, a keyless client past its budget may pay per call, only if the user has supplied a payer and agreed to pay:
- Send the HTTP header
Accept-Payment: x402. A call over budget then returns anisErrorresult whosestructuredContentis the x402PaymentRequireddocument. - Repeat the call with the signed payment in
_meta["x402/payment"]. It skips the budget, and the receipt comes back in_meta["x402/payment-response"]. A tool error is never charged.
tools/list and calls with a valid key are never priced. Without the header, nothing changes.