B20 LABS
Model Context Protocol · read + simulate

Give your AI assistant
B20 superpowers.

b20-operator is an MCP server that lets Claude, Cursor or any MCP client inspect and simulate B20 — Base's native token standard — in plain language. It never signs or moves funds: every write is a read-only simulation.

npm i @b20labs/mcp → Setup ↓

Add it in 10 seconds

Drop this into your Claude Desktop / Cursor MCP config, then restart:

{
  "mcpServers": {
    "b20-operator": {
      "command": "npx",
      "args": ["-y", "@b20labs/mcp"],
      "env": { "B20_RPC": "https://mainnet.base.org" }
    }
  }
}

Tip: set B20_RPC to a managed Base RPC (Alchemy/QuickNode) for burst-safe reads.

Ask it anything

inspect“Inspect the B20 at 0xb200…3418 — what is it and is it safe?”
simulate before signing“Will deploying a rug-proof ASSET token ‘Doge Base’ ($DOGEB, 1B supply) from 0xabc… succeed? Show the exact error if not.”
zero-RPC address“What address will an ASSET B20 get from deployer 0xabc… with salt 0x…01?”
decode a revert“Decode this B20 revert: 0x62975e6a…”
activation gate“Is the STABLECOIN variant activated on Base yet?”

Six tools

simulate_create_b20
Dry-run a deploy via eth_call → “would succeed” or the exact decoded revert (incl. failing initCall). No gas, no signature.
inspect_b20
Read a B20’s name, symbol, decimals, supply and variant from Base mainnet.
derive_b20_address
Zero-RPC: the deterministic address a B20 will get from (variant, deployer, salt).
decode_b20_error
Turn raw revert bytes into a typed error name + human message (all 48 precompile errors).
check_activation
Is a variant activated on Base — the only correct write-gate.
identify_b20
Zero-RPC: is an address a B20, and which variant.