Skip to content

bsc-token-preflight MCP server

com.brainonbnb/bsc-token-preflightbrainonbnb.comstreamable-httpv1.0.0Scanned

Honeypot and rug-pull check for any BNB Chain token before a trade, measured on chain, free

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 5 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the bsc-token-preflight MCP server can do

The bsc-token-preflight MCP server is published by brainonbnb.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: bsc_token_preflight and bsc_pool_scan), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 5 findings (base64-blob, long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 2Claude Code: ask
  • bsc_pool_scanThe full honeypot / rug-pull / liquidity read behind bsc_token_preflight, every figure and its source.2 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The input schema at properties.address.examples[0] contains a 42-character base64 string.

      Matched text

      inputSchema.properties.address.examples[0]: "0x0E09FaBB73Bd3Ade0a17ECC321fD13a19e81cE82"

      What this check looks for
    • Info

      The description is 3,088 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...nothing for a wallet holding 1,000,000 $BOBAI), sent as HTTP header X-Scan-Pass."

      What this check looks for
    Description, as the server wrote it
    The full honeypot / rug-pull / liquidity read behind bsc_token_preflight, every figure and its source. Use it when the preflight’s short answer is not enough (an audit, a dashboard, a second look at one figure); for the go/no-go before a trade call bsc_token_preflight, and for the route alone pancakeswap_best_route. Measure what a trade on BNB Smart Chain would actually cost, for ANY token or pool — before placing it. Reads the pool live from the chain and returns: real cost per trade size (price impact + swap fee + transfer tax together, not the headline slippage a router shows), the USD size that moves the price 1% in each direction, the transfer tax measured from executed trades (simulated on chain at that block when the pool has not traded in the last hour, and flagged measured:false) rather than taken from a label, how much of the token's liquidity the readable pool actually holds, and whether the LP is burned or still withdrawable — plus our own sell simulation on the router from a fresh address (sellability). A token still raising on four.meme with no pool yet is measured from four.meme's own contract instead (curve: raise progress, price, buy/sell cost per size, fee). Works on PancakeSwap V2, V3 and Infinity CL (an Infinity pool is found from its key on chain and priced by PancakeSwap's own Infinity quoter, its hook included), Uniswap V2 and V3, and Biswap; a token still on four.meme's or flap.sh's launch curve is read from that curve. Read tax.measured and tax.source before using the cost columns: a tax that could not be measured comes back null with a warning, never as 0%; quotable: false with a reason is an answer, not an error. Also returned: deeperPoolElsewhere (a bigger pool for the same token than the one read), tax.simulated (an independent cross-check next to the measured tax), lp.custody (who holds the LP of a V2 pair, wallet by wallet, the deployer flagged; complete from the pair's own logs when it is under an hour old; V3 positions not read), holders (the largest wallets with exchange, lock and burn addresses named apart, or unknown: true with the reason when there is no real list yet), age (pool and token, from the first block their code existed), activity (swaps, buys vs sells, unique traders, volume and the largest sell over the window read), flow (who sold over that window: the deployer and wallets it funded, netted against liquidity they added back to the same pair, top holders selling over a quarter of their balance, and for a pool under an hour old the launch-block buyers still holding), venues[] (the scanned pool first, pools under $100 left out) and contract.properties (the GoPlus contract flags, true/false/null, with the ones it did not check named). No API key; pool figures are never cached, contract properties (from GoPlus) for up to 6 h. Free for 1,000 scans per caller and UTC day; past that it answers code free_limit, and a day pass carries on (POST https://agent.brainonbnb.com/scan-pass: 0.50 USD1, half that in $BOBAI, nothing for a wallet holding 1,000,000 $BOBAI), sent as HTTP header X-Scan-Pass.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • bsc_token_preflightSTART HERE for any BSC token.3 findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The input schema at properties.address.examples[0] contains a 42-character base64 string.

      Matched text

      inputSchema.properties.address.examples[0]: "0x0E09FaBB73Bd3Ade0a17ECC321fD13a19e81cE82"

      What this check looks for
    • Info

      The description is 2,668 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...igures are never cached, the GoPlus contract flags and holder list for up to 6 h."

      What this check looks for
    • Warn

      The server marks "bsc_token_preflight" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false}; The description's first verb is "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    START HERE for any BSC token. Honeypot and rug-pull pre-trade check, measured not labelled: For an agent about to trade ANY token on BNB Smart Chain: the check to run before every trade, in one call and at YOUR size. Answers the two questions that matter before signing - can I get in, and can I get out again - and what the trip costs. Returns stop[] (facts that end an automated trade: the sell does not go through from a fresh address, nothing quotes, half the money is gone on an immediate round trip) and caution[] (facts to weigh, each with its figure and the line it was measured against: a transfer tax that is high, unknown or changeable by the owner; a size that moves the price more than 1%; a deeper pool elsewhere; LP that can still be withdrawn, and by whom - the deployer holding the LP is named - or that was already withdrawn; holders unknown or concentrated; the deployer or a wallet it funded selling into the pool (net of liquidity it added back), a top holder selling over a quarter of its balance, launch buyers holding over 10%; contract flags), then the figures: the token’s spot price in dollars from the pool read (token.price_usd), the best PancakeSwap route at this size, what you pay and receive, the slippage in bps this size really needs, per side, from the measured tax (a fee-on-transfer token reverts below its tax), the round trip with the transfer tax applied (measured from executed trades, or, when the pool has not traded in the window, simulated on chain at that block — the answer says which), the 1% depth in both directions, LP burned and who holds the rest, pool and token age, the swaps of the last hour and who sold in it (flow). A short answer, built from bsc_pool_scan and pancakeswap_best_route, which stay available under details for every figure behind it. A token still on its four.meme launch curve is answered from four.meme's own contract. It also reads who controls the contract on-chain (control: owner() / getOwner() and whether that owner is renounced, a plain wallet or a contract, an EIP-1967 proxy and its admin, a mint(address,uint256) function in the bytecode) and names an owner that is one wallet where the token has a tax, a mint function or a proxy. gate is the verdict in one word to branch on - stop, weigh or no_known_stop - and each stop/caution item with a figure carries it as value, line and unit. A refusal comes with a code (is_wallet, not_a_token, bad_address, bad_usd, ...) and a hint. It does not say "safe" and returns no score: it cannot see an owner who has not acted yet, and says so. No API key; pool figures are never cached, the GoPlus contract flags and holder list for up to 6 h.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:21 UTC, unchanged since Nov 2, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://brainonbnb.com/mcp/preflight: tools/list returned 2 tools to an anonymous client, including bsc_token_preflight (write), bsc_pool_scan (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

3 warn2 info
  • The input schema at properties.address.examples[0] contains a 42-character base64 string.

    Matched text

    inputSchema.properties.address.examples[0]: "0x0E09FaBB73Bd3Ade0a17ECC321fD13a19e81cE82"

    What this check looks for
  • The server marks "bsc_token_preflight" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false}; The description's first verb is "start": a word for a change.

    What this check looks for
  • The input schema at properties.address.examples[0] contains a 42-character base64 string.

    Matched text

    inputSchema.properties.address.examples[0]: "0x0E09FaBB73Bd3Ade0a17ECC321fD13a19e81cE82"

    What this check looks for
  • The description is 2,668 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...igures are never cached, the GoPlus contract flags and holder list for up to 6 h."

    What this check looks for
  • The description is 3,088 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...nothing for a wallet holding 1,000,000 $BOBAI), sent as HTTP header X-Scan-Pass."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http bsc-token-preflight https://brainonbnb.com/mcp/preflight
claude mcp add --transport http bsc-token-preflight https://brainonbnb.com/mcp/preflight

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__bsc-token-preflight__bsc_token_preflight",
      "mcp__bsc-token-preflight__bsc_pool_scan"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bsc-token-preflight. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.brainonbnb/bsc-token-preflight/verify?hash=02b97170ab0325fb196379f11d1cd000872e5a716202910fdc409e2065105869" | jq -e '.changed == false'

Pinned hash 02b97170ab03, from Nov 14, 2026, 14:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.brainonbnb/bsc-token-preflight/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.brainonbnb/bsc-token-preflight
[![Anlyon Radar](https://radar.anlyon.com/badge/com.brainonbnb/bsc-token-preflight.svg)](https://radar.anlyon.com/servers/com.brainonbnb/bsc-token-preflight)

Source: MCP Registry. Synced Nov 1, 2026, 14:17 UTC.

bsc-token-preflight MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the bsc-token-preflight MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the bsc-token-preflight MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the bsc-token-preflight MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the bsc-token-preflight MCP server have?

2 tools: 2 write. bsc_token_preflight and bsc_pool_scan.

Does the bsc-token-preflight MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the bsc-token-preflight MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the bsc-token-preflight MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.