Developer · Local MCP server
Binance Spot (security-first) + crypto analyst
Security-first Binance Spot MCP + honest crypto analyst. 25 tools, 5 prompts, human-gated orders.
Visit Binance Spot (security-first) + crypto analyst's website
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Alejandrehl/kainext-binance-mcp- Version
- 1.2.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-08-22
- Updated
- 2026-08-22
- Publisher
- Alejandrehl (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Alejandrehl) · how
- Listed under
- Binance MCP servers
- Website
- github.com/Alejandrehl/kainext-binance-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | kainext-binance-mcp | 1.2.1 | stdio |
How to connect Binance Spot (security-first) + crypto analyst
Binance Spot (security-first) + crypto analyst runs locally from a Python package published to PyPI: kainext-binance-mcp version 1.2.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx kainext-binance-mcp. It reads these environment variables: BINANCE_ENV (required), BINANCE_READ_API_KEY (required, secret) and BINANCE_READ_API_SECRET (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"kainext-binance-mcp": {
"command": "uvx",
"args": [
"kainext-binance-mcp"
],
"env": {
"BINANCE_ENV": "<value>",
"BINANCE_READ_API_KEY": "<secret>",
"BINANCE_READ_API_SECRET": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| BilincHosted agent memory with provenance, contradiction surfacing, and snapshot rollback. | Local · stdio |
| BiltAI agents autonomously build and deploy mobile apps through natural language workflows. | Remote · SSELive check: ✗ no handshake |
| BimDesign-review threads, comments, reactions and deployments from Bim. Sign in with Google. | Remote · HTTPLive check: sign-in required |
| BimhouseBim.house - words become buildings. Generate BIM, check code & structure, quote materials. | Remote · HTTPLive check: ✓ handshake |
| BinkyIsolated dev environments, one per git worktree: ports, env, and DB slices as agent tools. | Local · stdio |
| BiomodelsBioModels - the public repository of curated, executable mathematical models of biological systems… | Remote · HTTPLive check: ✓ handshake |
| BitbucketManage repositories, branches, webhooks, and pull requests in Bitbucket workspaces. | Local · stdio |
| Bitbucket MCPBitbucket Cloud MCP in Go: complete API auto-generated from spec, customizable prompts. | Local · stdio |