Skills bnbchain-mcp

📦

bnbchain-mcp

Name: bnbchain-mcp
Author: internet-court

v1.0.0 Content revision r1 High Risk 🔑 Env variables⚙️ External commands🌐 Network access

Connect BNB Chain MCP Tools

Developers need clear MCP setup and safe tool selection for BNB Chain work. This skill explains server configuration, tool parameters, and transaction safeguards.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "bnbchain-mcp" from https://skillstore.io/skills/internet-court-bnbchain-mcp.md and its manifest at https://skillstore.io/api/skills/internet-court-bnbchain-mcp/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/internet-court-bnbchain-mcp.md Signed manifest GET /api/skills/internet-court-bnbchain-mcp/manifest Signed lockfile GET /api/skills/internet-court-bnbchain-mcp/lockfile

Test it

Using "bnbchain-mcp". I want to inspect a BSC transaction hash.

Expected outcome:

Use the transaction analysis prompt or receipt tool with the BSC network. No private key is needed for this read-only task.

Using "bnbchain-mcp". I need to register my MCP server as an ERC-8004 agent.

Expected outcome:

Prepare the agent metadata URI, choose the exact network, confirm signer ownership, then call the registration tool only after confirmation.

Using "bnbchain-mcp". I want to upload a file to Greenfield mainnet.

Expected outcome:

Confirm the mainnet target, bucket name, file path, and signing wallet. Treat the action as a write that requires PRIVATE_KEY handling.

Security Audit

High Risk

v2 • 7/21/2026 Open versioned report

Static detections for private keys, shell execution, URLs, and address analysis are documentation-format false positives. The skill nevertheless enables high-impact blockchain writes and local file transfers, and it installs an unpinned npm package at runtime. Its explicit confirmation and key-handling guidance mitigate, but do not remove, these operational risks.

Files scanned

360

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (3)

High

SKILL.md:68 SKILL.md:114-115 references/greenfield-tools-reference.md:49

Financial and Irreversible Write Operations

The skill enables token transfers, token approvals, contract writes, and an irreversible Greenfield refund change. These actions can cause loss of funds or permanent account changes if the user confirms incorrect parameters.

The references expressly identify state-changing, irreversible operations, while the skill supplies confirmation guidance. The danger remains inherent to the supported operations.

Medium

SKILL.md:16 SKILL.md:34

Unpinned Runtime Package Installation

The setup instructs clients to run the latest npm package at runtime. A later package release can change the code executed by the MCP server.

The documented command uses @latest and the configuration repeats it. This is direct evidence of an unpinned dependency execution path.

Medium

references/greenfield-tools-reference.md:29-30 references/greenfield-tools-reference.md:34

Local File Transfer Through Greenfield Tools

Greenfield upload and download tools accept local file paths. Incorrect path selection can disclose local data to a bucket or overwrite a local destination.

The documentation explicitly supports absolute upload paths and download target paths. It does not show malicious intent, but the file-transfer capability has a clear data-handling impact.

Audited by: claude View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/internet-court-bnbchain-mcp/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/internet-court-bnbchain-mcp/security.svg)](https://skillstore.io/skills/internet-court-bnbchain-mcp?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/internet-court-bnbchain-mcp?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/internet-court-bnbchain-mcp/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/internet-court-bnbchain-mcp.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

internet-court. (2026). bnbchain-mcp security audit report (audit version 2) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/internet-court-bnbchain-mcp/audits/2

BibTeX citation

@techreport{internet-court-internet-court-bnbchain-mcp-2026,
  author = {internet-court},
  title = {bnbchain-mcp security audit report (audit version 2)},
  institution = {Skillstore},
  year = {2026},
  number = {2},
  url = {https://skillstore.io/skills/internet-court-bnbchain-mcp/audits/2},
  note = {Author version 1.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "bnbchain-mcp security audit report (audit version 2)"
version: "1.0.0"
type: report
authors:
  - name: "internet-court"
date-released: "2026-07-21"
url: "https://skillstore.io/skills/internet-court-bnbchain-mcp/audits/2"
identifiers:
  - type: other
    value: "skillstore:internet-court-bnbchain-mcp:audit:2"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Set up BNB Chain MCP access

Configure the MCP server, choose stdio or SSE mode, and understand where credentials belong.

Query EVM chain data

Select tools for blocks, transactions, balances, contract reads, token data, and NFT checks.

Plan guarded write workflows

Prepare transfers, approvals, contract writes, ERC-8004 updates, or Greenfield actions with explicit confirmation steps.

Try These Prompts

Begin With Read-Only Setup

Use the bnbchain-mcp skill to configure read-only BNB Chain MCP access. Explain the server setup, supported networks, and tools that do not need PRIVATE_KEY.

Choose the Right Query Tool

Use the bnbchain-mcp references to choose tools for analyzing this transaction, address, token, and contract. Explain required parameters and network choices.

Prepare an ERC-8004 Registration

Use the ERC-8004 reference to plan agent registration. List the required metadata, network choice, confirmation checks, and read-only verification tools.

Review a High-Risk Write Plan

Use the bnbchain-mcp skill to review this planned write operation. Check network, signer, recipient, amount, contract function, approval scope, and rollback limits.

Best Practices

Start in read-only mode and leave PRIVATE_KEY empty until a write is required.
Ask for an explicit network before every transfer, approval, contract write, ERC-8004 update, or Greenfield write.
Pin and review the MCP server package version before using it with real funds.

Avoid

Do not paste private keys into chat, logs, or reusable prompt text.
Do not default write operations to BSC mainnet when the user omits a network.
Do not use unlimited token approvals or unreviewed contract writes with production wallets.

Frequently Asked Questions

Does this skill require a private key?

Read-only tools do not require a private key. Transfers, approvals, contract writes, ERC-8004 writes, and Greenfield writes do require signing credentials.

Which MCP clients can use it?

The skill describes MCP server configuration for clients such as Claude Desktop, Cursor, Claude Code, and Codex environments that support MCP.

Can it query chains other than BNB Chain?

The references mention BSC, opBNB, Ethereum, Base, Polygon, and supported testnets where the MCP server exposes those networks.

Can it register an ERC-8004 agent?

Yes. It documents the registration, metadata URI, lookup, wallet, and URI update tools for ERC-8004 agent workflows.

Does it support Greenfield?

Yes. It covers bucket, object, folder, account, and payment tools for Greenfield testnet and mainnet workflows.

What is the main safety concern?

The main concern is combining private keys with irreversible blockchain write tools. Confirm network, amount, recipient, and contract details every time.