Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"zebpay": {
"env": {
"LOG_LEVEL": "info",
"ZEBPAY_API_KEY": "YOUR_API_KEY_HERE",
"ZEBPAY_API_SECRET": "YOUR_API_SECRET_HERE"
},
"args": [
"/absolute/path/to/zebpay-mcp-server/dist/index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'cp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked cp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in finance
MCP server for retrieving Japanese stock market data via J-Quants API v2
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
Swiss accounting integration for Bexio. 310 tools for invoices, contacts, projects.
Brazilian public procurement (PNCP) and Federal Revenue CNPJ data — 16 tools, 4 prompts.
MCP Security Weekly
Get CVE alerts and security updates for Zebpay MCP Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.

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
... [View full README on GitHub](https://github.com/zebpay/zebpay-mcp-server#readme)