Bellchain
Crypto alert chains in your AI assistant: check alerts, test ideas with the replay, build chains.
Description from the maker (original English)
Cross-DEX price & spread for PancakeSwap v2+v3 on BSC via x402. Tool get_dex_spread(pair, fee?).
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
EVM_PRIVATE_KEY, GATEWAY_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"bsc-dex-spread": {
"command": "npx",
"args": [
"-y",
"bsc-dex-spread-mcp"
],
"env": {
"EVM_PRIVATE_KEY": "your-value",
"GATEWAY_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add bsc-dex-spread --env EVM_PRIVATE_KEY=your-value --env GATEWAY_URL=your-value -- npx -y bsc-dex-spread-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"bsc-dex-spread": {
"command": "npx",
"args": [
"-y",
"bsc-dex-spread-mcp"
],
"env": {
"EVM_PRIVATE_KEY": "your-value",
"GATEWAY_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"bsc-dex-spread": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"bsc-dex-spread-mcp"
],
"env": {
"EVM_PRIVATE_KEY": "your-value",
"GATEWAY_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
GATEWAY_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account donnywin85, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: EVM_PRIVATE_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Bellchain, Quidli Connect, Diamond Bitcoin Intelligence
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Crypto alert chains in your AI assistant: check alerts, test ideas with the replay, build chains.
Resolve social handles to wallets, score onchain reputation, pay in any ERC-20, SPL or native.
Bitcoin MCP: fee budgets, retained-block inclusion proofs and risk checks. Free service discovery.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
One MCP tool — `get_dex_spread` — returning live cross-DEX price and spread for PancakeSwap v2 + v3 on BSC, paid $0.01 USDC per call from your own wallet.
Inspecting the server costs nothing and needs no wallet:
npx -y bsc-dex-spread-mcp
It starts on stdio and lists its one tool. Add it to Claude Code:
claude mcp add bsc-dex-spread --env EVM_PRIVATE_KEY=0xyour_disposable_base_key -- npx -y bsc-dex-spread-mcp
Without a key the tool is still listed, and a call tells you exactly what is missing rather than failing obscurely:
get_dex_spread failed: EVM_PRIVATE_KEY is not set. Add your funded Base-mainnet
buyer wallet key (0x-prefixed, USDC-only, low balance) to the MCP server env config.
Before you fund anything, know the free alternative. If you do not specifically need the paid, uncapped path, arb-dex-mcp and dex-data-mcp return cross-DEX spread keyless and free on six chains. This server exists for callers who want per-call billing with no free-tier ceiling — it is not the cheapest way in.
An MCP server that gives your agent one tool — `get_dex_spread` — returning real-time cross-DEX price & spread data for PancakeSwap v2 + v3 on BSC. Each call is a paid API call: $0.01 USDC on Base mainnet, settled automatically over x402 from *your own* wallet. No subscription, no account, no API key to request — the agent pays per call.
Backed by a live x402 gateway: https://x402.donnyautomation.com Public usage/proof page: https://x402.donnyautomation.com/stats
get_dex_spread(pair, fee?)Real-time cross-DEX price & spread for PancakeSwap v2+v3 on BSC.
pair (required) — token pair as SYM/SYM; the first symbol is the USD-priceable side. Examples: WBNB/USDC, WBNB/USDT, CAKE/WBNB.fee (optional) — a PancakeSwap v3 fee tier (100, 500, 2500, 10000) to restrict the v3 probe. Omit to probe all v3 tiers and v2.Returns per-venue prices, best buy / best sell venue, the gross cross-DEX spread in bps, liquidity (per-venue TVL + totals), and the source block number. Example:
{
"pair": "WBNB/USDC", "network": "bsc", "chainId": 56, "blockNumber": 107562007, "nativeUsd": 546.6, "pricesByVenue": [ { "venue": "pancake", "surface": "v2", "price": 546.6, "tvlUsd": 1234567 }, ... ], "bestBuy": { "venue": "pancakeV3:500", "price": ... }, "bestSell": { "venue": "biswap", "price": ... }, "midSpreadBps": 27.4, "crossDex": { "grossSpreadBps": 14.05, "buyVenue": "...", "sellVenue": "...", "surface": "v2v3" }, "liquidity": { "venues": 7, "totalTvlUsd": ... }, "ts": "2026-07-01T...", "source": "rpc" }
Cross-DEX spread is the raw signal behind arbitrage, best-execution routing, and slippage estimation. Instead of running BSC RPC infrastructure and multi-DEX pool math itself, an agent calls one tool and pays a cent for a fresh, block-stamped answer across PancakeSwap v2 + v3 venues.
You bring the wallet. This package ships no keys. The server signs each payment with a private key it reads from its own environment (EVM_PRIVATE_KEY), which you set in your MCP client's server config. That is the design: the buyer (you) pays for the data with the buyer's wallet.
eip155:8453).exact scheme is EIP-3009 transferWithAuthorization: you sign an off-chain USDC authorization and the facilitator broadcasts it and pays the gas. A 0-ETH wallet settles fine.npm install -g bsc-dex-spread-mcp
Add it to your MCP client. Claude Desktop / Claude Code (claude_desktop_config.json or .mcp.json):
{
"mcpServers": { "bsc-dex-spread": { "command": "npx", "args": ["-y", "bsc-dex-spread-mcp"], "env": { "EVM_PRIVATE_KEY": "0xYOUR_BASE_MAINNET_BUYER_KEY" } } } }
EVM_PRIVATE_KEY — your Base-mainnet buyer wallet key (0x-prefixed), funded with a few dollars of USDC on Base. Optional GATEWAY_URL overrides the endpoint (defaults to https://x402.donnyautomation.com).
Restart your client; the agent will have get_dex_spread available and will pay $0.01 USDC each time it calls it.
agent → get_dex_spread(pair)
→ GET https://x402.donnyautomation.com/call?pair=... (HTTP 402 PAYMENT-REQUIRED) → sign EIP-3009 USDC auth with EVM_PRIVATE_KEY → x402 facilitator settles on Base → gateway proxies to its BSC DEX reader → 200 with the cross-DEX payload
Checked against the published artifacts on 2026-08-21:
npm install -g bsc-dex-spread-mcp and npx -y bsc-dex-spread-mcp both install and start; npm 0.1.0 matches this repo.GET /call?pair=WBNB/USDC with a valid x402 V2 challenge — 402, a payment-required header, $0.01 USDC (10000 at 6 decimals) on Base eip155:8453.arb-dex-mcp (6 chains) or dex-data-mcp (22 tools).agent-utils-mcp.approval-queue-starter.MIT