Skip to content

internet-court/internet-court-skill / vendored/bnb-chain/bnbchain-mcp

bnbchain-mcp

Verified

BNB Chain MCP server connection and tool usage. Covers npx @bnb-chain/mcp@latest, PRIVATE_KEY and RPC, and every MCP tool — blocks, transactions, contracts, ERC20/NFT transfers, wallet, ERC-8004 agent registration, Greenfield. Use when connecting to bnbchain-mcp, querying or transacting on BNB Chain/opBNB/EVM, registering as ERC-8004 agent, or using Greenfield.

references/prompts-reference.md

View on GitHub
# MCP prompts reference

The BNB Chain MCP server exposes **prompts** that return guided analysis or explanations. Use these prompt names when invoking MCP prompts (e.g. from Cursor or Claude).

| Prompt name | When to use |
|-------------|-------------|
| **analyze_block** | User wants detailed information about a block (transactions, gas, etc.). |
| **analyze_transaction** | User wants analysis of a specific transaction (hash). |
| **analyze_address** | User wants analysis of an EVM address (balances, contracts, activity). |
| **interact_with_contract** | User needs guidance on how to interact with a smart contract (read/write, ABI, params). |
| **explain_evm_concept** | User asks about an EVM concept (gas, opcodes, ABI, etc.). |
| **compare_networks** | User wants to compare EVM-compatible networks (BSC, opBNB, Ethereum, etc.). |
| **analyze_token** | User wants to analyze an ERC20 or NFT token (metadata, supply, etc.). |
| **how_to_register_mcp_as_erc8004_agent** | User wants step-by-step guidance on registering an MCP server as an ERC-8004 agent. |

Prompts typically accept input (e.g. block number, tx hash, address) as specified by the MCP server. Prefer these prompts when the user asks for “analysis,” “explanation,” or “how to” rather than a single raw tool call.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall