Bnbchain (nirholas) MCP Server

@nirholas/bnbchain-mcp npm v1.0.1

Published by @nirholas — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
A
100/100
Last scanned
Trust
A · 100/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade

Started at 100 and nothing was deducted: the deterministic scan raised no scored threat in the published surface it inspected. Capability observations and advisory notes are recorded but never lower the score.

Findings 7

high Shell/command execution in server code (build/vendors/payments/tunnel/tunnel-manager.js)MTC-SRC-002

In the server's implementation (`build/vendors/payments/tunnel/tunnel-manager.js:215`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server build/vendors/payments/tunnel/tunnel-manager.js

high Shell/command execution in server code (build/vendors/tatum-api/cli.js)MTC-SRC-002

In the server's implementation (`build/vendors/tatum-api/cli.js:16`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server build/vendors/tatum-api/cli.js

high Shell/command execution in server code (examples/integrations/autogpt-plugin/plugin.py)MTC-SRC-002

In the server's implementation (`examples/integrations/autogpt-plugin/plugin.py:64`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: subprocess.Popen(

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server examples/integrations/autogpt-plugin/plugin.py

high Shell/command execution in server code (examples/integrations/langchain-agent.py)MTC-SRC-002

In the server's implementation (`examples/integrations/langchain-agent.py:62`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: subprocess.Popen(

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server examples/integrations/langchain-agent.py

high Shell/command execution in server code (src/vendors/dex-analytics/test.js)MTC-SRC-002

In the server's implementation (`src/vendors/dex-analytics/test.js:9`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/vendors/dex-analytics/test.js

high Shell/command execution in server code (src/vendors/dex-analytics/test_mcp_client.js)MTC-SRC-002

In the server's implementation (`src/vendors/dex-analytics/test_mcp_client.js:9`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/vendors/dex-analytics/test_mcp_client.js

medium Hardcoded egress to an external endpoint (build/sperax/tools/plugins.js)MTC-SRC-003

In the server's implementation (`build/sperax/tools/plugins.js:246`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch(`https://api.coingecko.com/api/v3/simple/price?ids=${coinId}&vs_currencies=${currency}&include_market_cap=true&include_24hr_vol=true&include_24hr_change=t

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server build/sperax/tools/plugins.js

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.1 latest A 100/100 7 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/nirholas-bnbchain-mcp/badge.svg)](https://mcptrustchecker.com/registry/nirholas-bnbchain-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/nirholas-bnbchain-mcp"><img src="https://mcptrustchecker.com/registry/nirholas-bnbchain-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/nirholas-bnbchain-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @nirholas/bnbchain-mcp --online

Use the free API → How scoring works

Other implementations of Bnbchain 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Finance & Commerce