Brain On BNB PancakeSwap MCP
An MCP server providing read-only access to PancakeSwap V3 data on BNB Chain, including fee tier analysis, liquidity position tracking, and best swap route calculation. It also includes pre-trade checks for token safety and rug-pull detection.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://brainonbnb.com/mcp/pancakeswapWhat its tools do
4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Passed Official MCP Registry namespace is tied to brainonbnb.com ·
- Passed Endpoint is on the registry namespace domain ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Check best swap route on BNB Chain
- Analyze PancakeSwap V3 fee tiers and positions
- Perform pre-trade token safety checks
- Scan pools for rug-pull risks
Source and maintenance
Protocol and capabilities
- Server
- PancakeSwap LP and Route (Brain on BNB) 1.0.0
- MCP protocol negotiated in check
- 2025-06-18
- Tools
- 4 advertised
- Resources
- 2 advertised
- Resource templates
- 0 advertised
- Prompts
- 2 advertised
{
"tools": {},
"prompts": {},
"resources": {}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
4 advertised
pancakeswap_fee_tiers
Measure which PancakeSwap fee tier of a pair actually pays liquidity providers, to decide WHERE to put liquidity. Use it before adding liquidity to a pair; once the pool is chosen use pancakeswap_range_plan for the price range, for a position you already hold use pancakeswap_position_look, and for a swap (not liquidity) use pancakeswap_best_route. Pass a token to compare all its pools against its main quote, or a pool address to pin the exact pair. A pair lives in up to five pools at once — V2 at 0.25% and V3 at 0.01%, 0.05%, 0.25% and 1.00% — and every source ranks them by the money already parked in them, which does not say which one pays. This measures each tier over a live window: swaps, turnover, the fees the pool actually paid out, and those fees per $1,000 of capital — over TWO denominators. The first is everything the pool holds, which is what every interface shows. The second is the capital standing within 2% of the current price, reconstructed by walking the tick book of the pool itself, because concentrated liquidity parked far from the price earns nothing and a new dollar only competes with the capital that is at the price. The two rankings disagree often, and both are returned. It also names tiers holding real money that did not trade at all. Measured, never annualised: the window is about an hour of chain and is reported with the answer. The same token asked again within 60 seconds gets the same measurement from the edge cache (cache.hit, cache.age_seconds). Read-only, free, no key; a tier whose pool could not be read is listed in tiers_unreadable and comparison_complete says whether every tier was measured.
{
"type": "object",
"required": [
"address"
],
"properties": {
"address": {
"type": "string",
"description": "A BSC token address (all of its PancakeSwap pools against its main quote are compared), or one PancakeSwap pool address to pin that exact pair; 0x + 40 hex"
}
},
"additionalProperties": false
}{
"readOnlyHint": true,
"destructiveHint": false
}pancakeswap_position_look
Look at any PancakeSwap V3 liquidity position on BNB Chain, read from the chain: in range or not and how much room is left to each edge, what it holds and is worth in BNB, the fees it is owed and whether collecting them pays for the gas, and what PancakeSwap’s The Flip proposal (LPs keeping 88% of swap fees) would change for it if adopted - the share the pool pays its LPs today is read from the pool itself. Give a position id, or a wallet that holds one (a wallet with several gets their ids back). Free. What to do about it - whether a re-set is due and in which width - is the paid plan of the DeFi Agent (ERC-8004 #363709), 0.10 USD1 or half that in $BOBAI.
{
"type": "object",
"properties": {
"address": {
"type": "string",
"description": "Or a wallet address that holds the position"
},
"position": {
"type": "string",
"description": "A PancakeSwap V3 position id (the NFT token id), digits only"
}
},
"additionalProperties": false
}{
"readOnlyHint": true,
"destructiveHint": false
}pancakeswap_range_plan
Replay real swaps to compare PRICE RANGE widths for a PancakeSwap V3 position: fees each width would have earned and how long it stayed in range. Use it after the pool is chosen (pancakeswap_fee_tiers picks the tier); for a position you already hold use pancakeswap_position_look. Read-only, free, no key. For a liquidity provider who has picked a PancakeSwap V3 pool and now has to pick a PRICE RANGE - the decision concentrated liquidity actually forces, and the one every interface answers with a preset. This does not model and does not forecast. It replays: the V3 Swap event carries the liquidity that was active when each trade went through, so a position of a stated size is walked through the swaps that really happened in a live window and asked, at each one, whether it was in range and what share of the active liquidity it was. Returns per candidate width the fees it would have collected, how much of the window it stayed in range, and how many times the price walked out. Impermanent loss is not in it, and it is worst exactly where the fees are best. The window is about an hour and travels with the answer.
{
"type": "object",
"required": [
"address"
],
"properties": {
"quote": {
"type": "string",
"description": "The other side of the pair, optional: BNB, USDT, USDC, USD1 or BUSD, or its address. Without it the quote with the deepest V3 pool is used, so pass it whenever a pair was named (CAKE/BNB)"
},
"address": {
"type": "string",
"description": "A BSC token address, or a PancakeSwap V3 pool address to pin the pool"
},
"capitalUsd": {
"type": "number",
"description": "Size of the position in dollars, optional - defaults to 1000. It sets your share of the active liquidity at each swap, so the fees depend on it"
}
},
"additionalProperties": false
}{
"readOnlyHint": true,
"destructiveHint": false
}pancakeswap_best_route
For an agent about to swap on PancakeSwap, and for the two questions it has to answer before signing. FIRST: which of the up-to-five pools the pair lives in actually returns the most AT THIS SIZE, quoted by the venue itself rather than ranked by depth - the deepest pool is regularly not the cheapest one for the trade being made. SECOND: what comes back if the proceeds are sold straight back on the same route, with the transfer tax (measured from executed trades, or simulated on chain when there was no trade to measure: transfer_tax.source says which) applied to the amounts carried between the legs, because the tax is taken outside the pool where no quoter can see it. Returns the best route, what every other route would have cost, the round trip with and without the tax, and the slippage this size really needs. It is not a safety certificate and does not use the word: it cannot see an owner who has not acted yet, and it says so.
{
"type": "object",
"required": [
"address"
],
"properties": {
"usd": {
"type": "number",
"description": "Trade size in dollars, optional - defaults to 250"
},
"address": {
"type": "string",
"description": "A BSC token address, or a PancakeSwap pool address to pin the pair"
}
},
"additionalProperties": false
}{
"readOnlyHint": true,
"destructiveHint": false
}Prompts
2 advertised
evaluate_bobai
Neutral due-diligence walkthrough of the $BOBAI token: routes through every read tool and ends with a balanced, on-chain-verified assessment (strengths AND risks).
prepare_bobai_swap
Step-by-step preparation of a $BOBAI swap on PancakeSwap V2 (fee-on-transfer safe): trade params, price impact for your size, wallet check, executable code.
- wallet
- BSC wallet address to check balances for (optional)
Resources
2 advertised
bobai_skill_doc
Machine-readable skill doc: identity, all tools, trade params, ready-to-run buy code, tokenomics
https://brainonbnb.com/skill.mdbobai_a2a_card
A2A agent card: skills and capabilities of the $BOBAI agent surface
https://brainonbnb.com/.well-known/agent-card.json30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 479 ms
- 95th percentile latency
- 479 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 479 ms · metadata changed · 4 tool(s), 2 resource(s), 0 resource template(s), 2 prompt(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http brain-on-bnb-pancakeswap-mcp https://brainonbnb.com/mcp/pancakeswapCodex
codex mcp add brain-on-bnb-pancakeswap-mcp --url https://brainonbnb.com/mcp/pancakeswapCursor
{
"mcpServers": {
"brain-on-bnb-pancakeswap-mcp": {
"url": "https://brainonbnb.com/mcp/pancakeswap"
}
}
}Cline
{
"mcpServers": {
"brain-on-bnb-pancakeswap-mcp": {
"type": "streamableHttp",
"url": "https://brainonbnb.com/mcp/pancakeswap",
"disabled": false
}
}
}VS Code
{
"servers": {
"brain-on-bnb-pancakeswap-mcp": {
"type": "http",
"url": "https://brainonbnb.com/mcp/pancakeswap"
}
}
}Gemini CLI
gemini mcp add --transport http brain-on-bnb-pancakeswap-mcp https://brainonbnb.com/mcp/pancakeswapClaude Desktop
https://brainonbnb.com/mcp/pancakeswapWindsurf
{
"mcpServers": {
"brain-on-bnb-pancakeswap-mcp": {
"serverUrl": "https://brainonbnb.com/mcp/pancakeswap"
}
}
}Let your agent find its tools
Find servers like Brain On BNB PancakeSwap MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other ai and machine learning servers
Do you run Brain On BNB PancakeSwap MCP?
Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.