@true402.dev/mcp-server

token_report_bsc

Instructions

The flagship composite for a BNB Smart Chain (BSC) ERC-20 — one call instead of five. Runs the full token-safety check (ERC-20 conformance, ownership, mint-capability, WBNB/USDC liquidity depth, buy/sell honeypot simulation), and returns a single avoid|caution|ok verdict with reasons plus the underlying reports. POST { token }. Cheaper than buying token-safety + liquidity-pulls + whale-swaps separately. Unpaid: free while the caller's IP has free-trial calls left that day (a small daily allowance shared across the trial stalls, no wallet); otherwise returns 402. Recent liquidity-removal and whale-swap activity is tracked on Base only, so recentPulls and recentWhaleSwaps are always empty on this chain. (PAID x402 service — USDC on Base; the MCP server needs a funded wallet to settle.) Price: $0.008 USD (fixed).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>"
    },
    "name": "token_report_bsc"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Chain to check; only 'bsc' is supported on this endpoint (default)
`token`	Yes	ERC-20 contract address (0x…) on BNB Smart Chain (BSC)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.3.0Oct 22, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and does so well: it discloses the safety checks performed, the verdict output, the free-trial/402 payment behavior, the x402 USDC-on-Base settlement requirement, the fixed price, and the BSC-only data limitation. The only minor omission is an explicit read-only statement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads the composite purpose and verdict output, then adds payment and chain-caveat details that are genuinely useful for invocation. It is slightly long and parenthetical, but no sentence is clearly wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description supplies enough for an agent to select and invoke the tool: scope, bundled checks, verdict output shape, pricing/auth model, and chain-specific limitations. The exact fields inside 'underlying reports' are vague, but that is not essential for selecting or calling the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both the chain and token parameters. The description repeats 'POST {token}' but adds no syntax or meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it 'runs the full token-safety check' for a BSC ERC-20 and returns an avoid|caution|ok verdict. It distinguishes itself from separate sibling tools by naming the token-safety, liquidity-pulls, and whale-swaps components it bundles.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames this as a one-call alternative to separate tools and notes the cost advantage, which gives clear usage context. It also warns that recentPulls and recentWhaleSwaps are always empty on BSC, but it does not give a direct 'use sibling X instead when...' exclusion rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.