Binance Spot (security-first) + crypto analyst
PYPI · KAINEXT-BINANCE-MCP
Security-first Binance Spot MCP + honest crypto analyst. 25 tools, 5 prompts, human-gated orders.
Available components
Last scanned (1 hour ago)
Scores higher than 6% of PyPI servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security32
- Malware scan not yet available for this package.Unverified
- CVE check failed: a known high-severity CVE affects mcp 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 55 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency74
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to Alejandrehl/kainext-binance-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 57 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 −6
- CVE-2026-59951 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 13 Oct 26 −4
- Malware scan: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.99 ▲ functional
- 12 Oct 26 +4
- Known CVEs: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: 0.99 → unverified ▼ functional
- 1 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Sept 26 −5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 25 Sept 26 −15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 19 Oct 2026 · Analysed pypi/kainext-binance-mcp@1.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Alejandrehl/kainext-binance-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Alejandrehl/kainext-binance-mcp/.github/workflows/release.yml@refs/tags/v1.2.1 |
| Rekor log index | 2567904967 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:984b8c33b57e7cb189cde8c28640d817421ad8d7dcf7e89e6047dec2a66d0a11 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-84m7-p3x7-pcfv | CVE-2026-59951 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 55 packages
| Packages resolved | 55 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the Binance Spot (security-first) + crypto analyst MCP server?
Binance Spot (security-first) + crypto analyst runs locally as a PyPI package, launched with uvx kainext-binance-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · kainext-binance-mcp
claude mcp add alejandrehl-kainext-binance-mcp -- uvx kainext-binance-mcp
What is the Binance Spot (security-first) + crypto analyst MCP server?
Binance Spot (security-first) + crypto analyst is an MCP server listed in the public MCP registry as io.github.Alejandrehl/kainext-binance-mcp. Security-first Binance Spot MCP + honest crypto analyst. 25 tools, 5 prompts, human-gated orders. This page covers its PyPI package (kainext-binance-mcp).
Is the Binance Spot (security-first) + crypto analyst MCP server safe to use?
Binance Spot (security-first) + crypto analyst scores 24 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 19 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the Binance Spot (security-first) + crypto analyst MCP server still maintained?
Binance Spot (security-first) + crypto analyst is still listed as active in the MCP registry. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Binance Spot (security-first) + crypto analyst MCP server under?
Binance Spot (security-first) + crypto analyst declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.