ZebPay MCP Server

io.github.ZebpayRajeshPublished by GitHub account ZebpayRajeshv1.0.2Updated Oct 24, 2026

MCP server for ZebPay crypto exchange — fetch prices, balances, and manage orders

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant read ZebPay crypto market data, check balances, and place or cancel spot and futures orders.

What you can do
A local stdio MCP server for the ZebPay crypto exchange covering spot and futures APIs. Public tools fetch tickers, order books, trades, klines, exchange info, markets, and 24h tickers. Private tools read balances, open orders, positions, and history, and can place market or limit orders, cancel orders, and add or reduce margin. It also exposes MCP resources and prompts, with request validation, retries, and optional file logging.
When to use it
Use it when you want an assistant to monitor ZebPay spot or futures markets, review account balances, positions, and order history, or place and manage orders through conversation. It is aimed at local MCP clients such as Cursor or Claude Desktop rather than hosted or web use.
Requirements
Runs locally as an npm package over stdio; needs Node.js 20+ and npm 9+. Private tools require a ZebPay API key and secret supplied as the environment variables ZEBPAY_API_KEY and ZEBPAY_API_SECRET, plus outbound network access to ZebPay API endpoints. Base URLs, transport, log level, timeout, and retry count are also configured by environment variables.
Before you install
The server holds exchange credentials that can trade: ZEBPAY_API_KEY and ZEBPAY_API_SECRET. Trading tools place and cancel real orders and can move funds, so permissions and IP whitelisting should be least-privilege and read-only unless trading is intended. Secrets are shown once at creation and must not be committed; rotate them if exposed. Optional file logging may record activity, so keep logs out of version control and redact secrets.

Installation

In SourceWeft

  1. Open ZebPay MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Zebpay MCP Server

[AI Trading Made Simple]

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.

What This Server Provides

  • Public market data tools (spot + futures)
  • Private trading/account tools (requires API credentials)
  • MCP resources and prompts for agent workflows
  • Request validation via Zod
  • Structured error handling and optional file logging

Features

  • Stdio-only MCP server for secure local integration with MCP clients
  • Spot and futures API coverage for both public and authenticated operations
  • HMAC-based authenticated request flow for private endpoints
  • Input validation and normalized MCP error responses
  • Outbound request retries and timeout controls
  • Optional structured file logging for debugging and auditability

Supported Tools

Spot (Public + Private)

  • Market data: tickers, order book, trades, klines, exchange info, currencies
  • Trading: place market/limit orders, cancel orders, cancel by symbol, cancel all
  • Account: balances, open orders, order history, trade history, exchange fee
  • Example tool names:
    • zebpay_public_getTicker
    • zebpay_public_getOrderBook
    • zebpay_spot_placeMarketOrder
    • zebpay_spot_placeLimitOrder
    • zebpay_spot_getBalance

Futures (Public + Private)

  • Market data: health status, markets, market info, order book, 24h ticker, aggregate trades
  • Trading/account: wallet balance, place order, add/reduce margin, open orders, positions
  • History: order history, linked orders, trade history, transaction history
  • Example tool names:
    • zebpay_futures_public_getMarkets
    • zebpay_futures_public_getOrderBook
    • zebpay_futures_placeOrder
    • zebpay_futures_getWalletBalance
    • zebpay_futures_getPositions

Tech Stack

  • Node.js (ESM)
  • TypeScript
  • @modelcontextprotocol/sdk
  • undici
  • zod

Project Structure

text
src/├── 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

Prerequisites

  • Node.js 20+
  • npm 9+
  • Zebpay API credentials (for private tools)
  • Create your API key/secret from the official ZebPay API portal: https://api.zebpay.com/

Creating a ZebPay API Key

Use the steps below to generate API credentials for this MCP server:

  1. Open the ZebPay API portal: https://api.zebpay.com/
  2. Sign in to your ZebPay account.
  3. Go to API Trading and click Create New API Key.
  4. Enter key details:
    • key name (for example: zebpay-mcp-local)
    • required permissions (read-only for market/account checks, trading permissions only if needed)
    • optional IP whitelist (recommended for better security)
  5. Complete OTP verification.
  6. Copy and save:
    • API Key
    • Secret Key (shown once)

Then add them to your local .env file:

env
ZEBPAY_API_KEY=your_api_keyZEBPAY_API_SECRET=your_api_secret

Security notes:

  • Never commit API keys/secrets to git.
  • Prefer least-privilege API permissions.
  • Rotate keys immediately if exposed.

Setup

bash
git clone <your-repo-url>cd zebpay-mcp-servernpm installcp env.example .env

Update .env (all values are read from environment; there are no fallback defaults in code):

env
ZEBPAY_API_KEY=your_api_key    # Use the API key from the step aboveZEBPAY_API_SECRET=your_api_secret    # Use the Secret key from the step aboveZEBPAY_SPOT_BASE_URL=https://sapi.zebpay.com/api/v2ZEBPAY_FUTURES_BASE_URL=https://futuresbe.zebpay.com/api/v1ZEBPAY_MARKET_BASE_URL=https://www.zebapi.com/api/v1/marketMCP_TRANSPORTS=stdioLOG_LEVEL=infoHTTP_TIMEOUT_MS=15000HTTP_RETRY_COUNT=2

Build and Run

bash
npm run buildnpm start

Optional logging to file:

bash
npm run start:log

MCP Client Configuration (Stdio)

Example MCP client config:

json
{  "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"      }    }  }}

[Install in Cursor]

Also see: mcp-config.json.example.

Environment Variables

VariableRequiredDescriptionExample value
ZEBPAY_API_KEYYesZebpay API key (required for private tools)YOUR_API_KEY_HERE
ZEBPAY_API_SECRETYesZebpay API secret (required for private tools)YOUR_API_SECRET_HERE
MCP_TRANSPORTSYesMust be stdiostdio
ZEBPAY_SPOT_BASE_URLYesSpot API base URLhttps://www.zebapi.com/api/v2
ZEBPAY_FUTURES_BASE_URLYesFutures API base URLhttps://futures-api.zebpay.com/api/v1
ZEBPAY_MARKET_BASE_URLYesMarket API base URLhttps://www.zebapi.com/api/v1/market
LOG_LEVELYesdebug, info, warn, errorinfo
LOG_FILENoFile path for logslogs/mcp-server.log
HTTP_TIMEOUT_MSYesOutbound request timeout (ms)15000
HTTP_RETRY_COUNTYesRetry count for outbound requests2

Developer Commands

bash
npm run buildnpm testnpm run test:watchnpm run logsnpm run logs:watchnpm run logs:errorsnpm run logs:statsnpm run logs:clear

Logging

  • Log tools and examples: scripts/README.md
  • Full logging docs: docs/LOGGING.md
  • Keep logs out of git (logs/ is ignored)

Issues

Found a bug or want to request a feature?

  • Create an issue from the GitHub Issues tab for this repository.
  • You can also use direct links after replacing <your-org> and <your-repo>:
    • Bug report: https://github.com/<your-org>/<your-repo>/issues/new?template=bug_report.md
    • Feature request: https://github.com/<your-org>/<your-repo>/issues/new?template=feature_request.md
  • Include these details for faster triage:
    • MCP client used (Cursor/Claude Desktop/other)
    • Node.js version and OS
    • Minimal reproduction steps
    • Relevant logs (redact secrets)

License

MIT

Source: README.md at commit c5c6f67

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.