crypto-payer-mcp
MCP server for cryptocurrency payment integration, enabling payment requests, webhook verification, and payment URL building.
README
Crypto Payer MCP Server
MCP (Model Context Protocol) Server for Crypto Payer Solution - cryptocurrency payment integration.
Quick Start
1. Create Configuration File
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
./.env
Example .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.com
2. Configure Claude Desktop
Add 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.
Advanced: Custom .env Path
{
"mcpServers": {
"crypto-payer": {
"command": "npx",
"args": ["-y", "crypto-payer-mcp"],
"env": {
"CRYPTO_PAYER_ENV_FILE": "/path/to/your/.env"
}
}
}
}
Configuration File Locations
The server searches for .env file in this order:
CRYPTO_PAYER_ENV_FILEenvironment variable (if set)./.env(current working directory)~/.crypto-payer-mcp.env(home directory)~/.config/crypto-payer-mcp/.env(XDG config)
Available Tools
| Tool | Description |
|---|---|
request_payment |
Request a new payment session from PLATFORM |
generate_auth_header |
Generate X-Operator-Authorization header |
verify_webhook |
Verify webhook signature (RSA-SHA512) |
build_payment_url |
Build payment page URL |
parse_webhook_event |
Parse webhook event data |
get_config |
Get current configuration (shows loaded .env path) |
Environment Variables
| Variable | Required | Description |
|---|---|---|
CRYPTO_PAYER_OPERATOR_ID |
Yes | Operator ID from PLATFORM |
CRYPTO_PAYER_SECRET_KEY |
Yes | Secret key from PLATFORM |
CRYPTO_PAYER_PUBLIC_KEY |
Yes | RSA public key for webhook verification |
CRYPTO_PAYER_OPERATOR_NAME |
Yes | Your operator display name |
CRYPTO_PAYER_API_URL |
No | API URL (default: testnet) |
CRYPTO_PAYER_DOMAIN_URL |
No | Domain URL (default: testnet) |
CRYPTO_PAYER_ENV_FILE |
No | Custom path to .env file |
API Endpoints
| Environment | API URL | Domain URL |
|---|---|---|
| Testnet | https://dev-api.bclass-solution.com/v1 |
https://dev-front.bclass-solution.com |
| Mainnet | https://api.bclass-solution.com/v1 |
https://bclass-solution.com |
Usage Examples
1. Check Configuration
Tool: get_config
Output: {
"envFile": "/Users/you/.crypto-payer-mcp.env",
"platformApiUrl": "https://dev-api.bclass-solution.com/v1",
"operatorId": "260f52c4...",
"operatorSecretKey": "****",
"isConfigured": true
}
2. Request Payment
Tool: request_payment
Input: { "userAccessToken": "user-jwt-token-from-your-system" }
Output: {
"result": true,
"data": { "paymentId": "eGrtTN7mIHTtd0uNLGnPweKtz2qXcVoq" }
}
3. Build Payment URL
Tool: build_payment_url
Input: { "paymentId": "eGrtTN7mIHTtd0uNLGnPweKtz2qXcVoq" }
Output: {
"url": "https://dev-front.bclass-solution.com?paymentId=xxx&id=xxx&name=xxx"
}
4. Verify Webhook
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" }
5. Parse Webhook Event
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" }
}
Supported Webhook Events
Deposit Events
DEPOSIT_PROCESSING- Deposit is being processedDEPOSIT_COMPLETED- Deposit completed successfully
Withdraw Events
WITHDRAW_REQUESTED- Withdrawal requested by userWITHDRAW_REJECTED- Withdrawal rejected by adminWITHDRAW_APPROVED- Withdrawal approved by adminWITHDRAW_PENDING- Withdrawal pendingWITHDRAW_PROCESSING- Withdrawal being processedWITHDRAW_COMPLETED- Withdrawal completedWITHDRAW_FAILED- Withdrawal failed
Development
# 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 start
License
MIT - see LICENSE
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.