Server data from the Official MCP Registry
MCP server for ZebPay crypto exchange — fetch prices, balances, and manage orders
MCP server for ZebPay crypto exchange — fetch prices, balances, and manage orders
Valid MCP server (1 strong, 2 medium validity signals). 5 known CVEs in dependencies (0 critical, 3 high severity) Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
4 files analyzed · 6 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: ZEBPAY_API_KEY
Environment variable: ZEBPAY_API_SECRET
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-zebpayrajesh-zebpay-mcp-server": {
"env": {
"ZEBPAY_API_KEY": "your-zebpay-api-key-here",
"ZEBPAY_API_SECRET": "your-zebpay-api-secret-here"
},
"args": [
"-y",
"mcp-zebpay-server"
],
"command": "npx"
}
}
}From the project's GitHub README.

Production-ready TypeScript MCP (Model Context Protocol) server for Zebpay spot and futures APIs, using stdio transport only. Model Context Protocol (MCP) is a standard way for AI assistants to securely call tools and data sources. It is designed for MCP clients like Cursor, Claude Desktop, and MCP Inspector that connect through local process execution. The server provides both market-data and trading workflows with strict validation, safe error handling, and developer-friendly observability.
zebpay_public_getTickerzebpay_public_getOrderBookzebpay_spot_placeMarketOrderzebpay_spot_placeLimitOrderzebpay_spot_getBalancezebpay_futures_public_getMarketszebpay_futures_public_getOrderBookzebpay_futures_placeOrderzebpay_futures_getWalletBalancezebpay_futures_getPositions@modelcontextprotocol/sdkundicizodsrc/
├── index.ts # Stdio MCP server entrypoint
├── mcp/ # Tools, resources, prompts, MCP errors/logging
├── private/ # Authenticated Zebpay clients
├── public/ # Public market-data clients
├── security/ # Credentials + signing helpers
├── http/ # Shared outbound HTTP client to Zebpay APIs
├── validation/ # Schemas and validation helpers
├── utils/ # Caching, metrics, formatting, file logging
└── types/ # Shared response types
https://api.zebpay.com/Use the steps below to generate API credentials for this MCP server:
https://api.zebpay.com/zebpay-mcp-local)Then add them to your local .env file:
ZEBPAY_API_KEY=your_api_key
ZEBPAY_API_SECRET=your_api_secret
Security notes:
git clone <your-repo-url>
cd zebpay-mcp-server
npm install
cp env.example .env
Update .env (all values are read from environment; there are no fallback defaults in code):
ZEBPAY_API_KEY=your_api_key # Use the API key from the step above
ZEBPAY_API_SECRET=your_api_secret # Use the Secret key from the step above
ZEBPAY_SPOT_BASE_URL=https://sapi.zebpay.com/api/v2
ZEBPAY_FUTURES_BASE_URL=https://futuresbe.zebpay.com/api/v1
ZEBPAY_MARKET_BASE_URL=https://www.zebapi.com/api/v1/market
MCP_TRANSPORTS=stdio
LOG_LEVEL=info
HTTP_TIMEOUT_MS=15000
HTTP_RETRY_COUNT=2
npm run build
npm start
Optional logging to file:
npm run start:log
Example MCP client config:
{
"mcpServers": {
"zebpay": {
"command": "node",
"args": [
"/absolute/path/to/zebpay-mcp-server/dist/index.js"
],
"env": {
"ZEBPAY_API_KEY": "YOUR_API_KEY_HERE",
"ZEBPAY_API_SECRET": "YOUR_API_SECRET_HERE",
"LOG_LEVEL": "info"
}
}
}
}
Also see: mcp-config.json.example.
| Variable | Required | Description | Example value |
|---|---|---|---|
ZEBPAY_API_KEY | Yes | Zebpay API key (required for private tools) | YOUR_API_KEY_HERE |
ZEBPAY_API_SECRET | Yes | Zebpay API secret (required for private tools) | YOUR_API_SECRET_HERE |
MCP_TRANSPORTS | Yes | Must be stdio | stdio |
ZEBPAY_SPOT_BASE_URL | Yes | Spot API base URL | https://www.zebapi.com/api/v2 |
ZEBPAY_FUTURES_BASE_URL | Yes | Futures API base URL | https://futures-api.zebpay.com/api/v1 |
ZEBPAY_MARKET_BASE_URL | Yes | Market API base URL | https://www.zebapi.com/api/v1/market |
LOG_LEVEL | Yes | debug, info, warn, error | info |
LOG_FILE | No | File path for logs | logs/mcp-server.log |
HTTP_TIMEOUT_MS | Yes | Outbound request timeout (ms) | 15000 |
HTTP_RETRY_COUNT | Yes | Retry count for outbound requests | 2 |
npm run build
npm test
npm run test:watch
npm run logs
npm run logs:watch
npm run logs:errors
npm run logs:stats
npm run logs:clear
scripts/README.mddocs/LOGGING.mdlogs/ is ignored)Found a bug or want to request a feature?
<your-org> and <your-repo>:
https://github.com/<your-org>/<your-repo>/issues/new?template=bug_report.mdhttps://github.com/<your-org>/<your-repo>/issues/new?template=feature_request.mdMIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
by mcp-marketplace · Developer Tools
Scaffold, build, and publish TypeScript MCP servers to npm — conversationally
by mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.