Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@crypto-payer-mcp Request a payment for user token abc123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP (Model Context Protocol) Server for Crypto Payer Solution - cryptocurrency payment integration.
Create .env file in one of these locations:
# Option 1: Home directory (recommended)
~/.crypto-payer-mcp.env
# Option 2: XDG config directory
~/.config/crypto-payer-mcp/.env
# Option 3: Current working directory
./.envExample .env file:
# Required
CRYPTO_PAYER_OPERATOR_ID=your-operator-id
CRYPTO_PAYER_SECRET_KEY=your-secret-key
CRYPTO_PAYER_OPERATOR_NAME=Your Operator Name
CRYPTO_PAYER_PUBLIC_KEY="-----BEGIN PUBLIC KEY-----\nMIICIjAN...\n-----END PUBLIC KEY-----"
# Optional (defaults to testnet)
CRYPTO_PAYER_API_URL=https://dev-api.bclass-solution.com/v1
CRYPTO_PAYER_DOMAIN_URL=https://dev-front.bclass-solution.comAdd to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"crypto-payer": {
"command": "npx",
"args": ["-y", "crypto-payer-mcp"]
}
}
}That's it! The server automatically loads configuration from your .env file.
{
"mcpServers": {
"crypto-payer": {
"command": "npx",
"args": ["-y", "crypto-payer-mcp"],
"env": {
"CRYPTO_PAYER_ENV_FILE": "/path/to/your/.env"
}
}
}
}Related MCP server: vnpay-mcp
The server searches for .env file in this order:
CRYPTO_PAYER_ENV_FILE environment variable (if set)
./.env (current working directory)
~/.crypto-payer-mcp.env (home directory)
~/.config/crypto-payer-mcp/.env (XDG config)
Tool | Description |
| Request a new payment session from PLATFORM |
| Generate X-Operator-Authorization header |
| Verify webhook signature (RSA-SHA512) |
| Build payment page URL |
| Parse webhook event data |
| Get current configuration (shows loaded .env path) |
Variable | Required | Description |
| Yes | Operator ID from PLATFORM |
| Yes | Secret key from PLATFORM |
| Yes | RSA public key for webhook verification |
| Yes | Your operator display name |
| No | API URL (default: testnet) |
| No | Domain URL (default: testnet) |
| No | Custom path to .env file |
Environment | API URL | Domain URL |
Testnet |
|
|
Mainnet |
|
|
Tool: get_config
Output: {
"envFile": "/Users/you/.crypto-payer-mcp.env",
"platformApiUrl": "https://dev-api.bclass-solution.com/v1",
"operatorId": "260f52c4...",
"operatorSecretKey": "****",
"isConfigured": true
}Tool: request_payment
Input: { "userAccessToken": "user-jwt-token-from-your-system" }
Output: {
"result": true,
"data": { "paymentId": "eGrtTN7mIHTtd0uNLGnPweKtz2qXcVoq" }
}Tool: build_payment_url
Input: { "paymentId": "eGrtTN7mIHTtd0uNLGnPweKtz2qXcVoq" }
Output: {
"url": "https://dev-front.bclass-solution.com?paymentId=xxx&id=xxx&name=xxx"
}Tool: verify_webhook
Input: {
"signature": "base64-signature-from-header",
"webhookBody": {
"event": "DEPOSIT_COMPLETED",
"timestamp": 1746776884590,
"data": { "user": {...}, "result": {...} }
}
}
Output: { "isValid": true, "event": "DEPOSIT_COMPLETED", "message": "Signature verified" }Tool: parse_webhook_event
Input: {
"webhookBody": {
"event": "DEPOSIT_COMPLETED",
"timestamp": 1746776884590,
"data": {
"user": { "id": "user_123", "name": "john" },
"result": { "id": "tx_abc", "amount": { "amount": "100" }, "instrument": { "symbol": "USDT" } }
}
}
}
Output: {
"eventType": "DEPOSIT_COMPLETED",
"category": "deposit",
"status": "completed",
"user": { "id": "user_123", "name": "john" },
"amount": { "amount": "100", "currency": "USDT", "network": "Ethereum" }
}DEPOSIT_PROCESSING - Deposit is being processed
DEPOSIT_COMPLETED - Deposit completed successfully
WITHDRAW_REQUESTED - Withdrawal requested by user
WITHDRAW_REJECTED - Withdrawal rejected by admin
WITHDRAW_APPROVED - Withdrawal approved by admin
WITHDRAW_PENDING - Withdrawal pending
WITHDRAW_PROCESSING - Withdrawal being processed
WITHDRAW_COMPLETED - Withdrawal completed
WITHDRAW_FAILED - Withdrawal failed
# Clone the repository
git clone https://github.com/syamai/crypto-payer-mcp.git
cd crypto-payer-mcp
# Install dependencies
npm install
# Create local .env for testing
cp .env.example .env
# Edit .env with your credentials
# Build
npm run build
# Run locally
npm startMIT - see LICENSE
Build the complete payment URL for redirecting users to the PLATFORM payment page. Combines the platform domain with paymentId and operator information.
Inputs: paymentId (required), operatorId, operatorName.
Generate the X-Operator-Authorization header value for PLATFORM API requests. Uses SHA-512 hash of operator credentials encoded in Base64.
Inputs: operatorId, operatorSecretKey.
Get the current Crypto Payer configuration (with sensitive values masked). Useful for debugging and verifying environment setup.
Inputs: no named parameters.
Parse and extract information from a webhook event. Returns structured data about the transaction including user, amount, network, and status.
Inputs: webhookBody (required).
Request a new payment session from Crypto Payer PLATFORM. Returns a paymentId that can be used to construct the payment URL. Requires user access token for authentication.
Inputs: userAccessToken (required).
Verify the signature of a webhook event from PLATFORM. Uses RSA-SHA512 signature verification with the operator's public key.
Inputs: signature (required), webhookBody (required), publicKey.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
Each tool targets a distinct action: payment session creation, auth header generation, webhook signature verification, URL construction, webhook parsing, and config retrieval. Even closely related webhook tools are separated by verification versus parsing, and request_payment versus build_payment_url are clearly different stages.
All tool names follow a consistent verb_noun snake_case pattern: request_, generate_, verify_, build_, parse_, get_. There are no mixed conventions or vague verbs.
Six tools is a well-scoped set for a payment integration server. Each tool covers a distinct part of the payment flow without redundancy or bloat.
The set covers the core flow: create a payment request, build the redirect URL, generate API auth, and verify/parse incoming webhooks. A notable gap is the lack of a direct payment-status lookup or cancellation/refund operation, though webhooks may partially cover status delivery.
Official BlindPay MCP server: stablecoin payouts, payins, quotes and customers for global payments.
MCP server with quote and live cryptocurrency price tools, local and cloud-deployed transports.
Billing proxy for MCP servers. Adds Stripe and x402 crypto payments without writing billing code.
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.