crypto-payer-mcp
Click on "Install 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-mcpRequest 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.
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
./.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.com2. 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"
}
}
}
}Related MCP server: btcpay-mcp
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 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) |
Environment Variables
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 |
API Endpoints
Environment | API URL | Domain URL |
Testnet |
|
|
Mainnet |
|
|
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 startLicense
MIT - see LICENSE
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityFmaintenanceA comprehensive Model Context Protocol (MCP) server for BTCPayServer integration, providing tools for payment processing, store management, user administration, webhook handling and more with full API coverage.Last updated3193MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables AI agents to manage merchant payment processing through the BTCPay Server Greenfield REST API. It supports tools for creating invoices, managing stores, tracking payments, and performing Lightning Network operations.Last updated21MIT
- FlicenseAqualityBmaintenanceAccept crypto payments on Algorand, VOI, Hedera & Stellar. Create hosted checkout links, verify on-chain payments, and generate MPP/x402/AP2 challenges from any MCP client. Supports all 16 AlgoVoi networks (USDC + native on mainnet + testnet).Last updated111
- AlicenseBqualityDmaintenanceMCP server for VNPay payment gateway (Vietnam). Supports payment URL generation, transaction queries, refunds, tokenized payments, and IPN verification with HMAC-SHA512 signing.Last updated86MIT
Related MCP Connectors
MCP server integrating with Stripe - tools for customers, products, payments, and more.
A paid remote MCP for hosted MCP server, built to return verdicts, receipts, usage logs, and audit-r
A paid remote MCP for CLI tool MCP, built to return verdicts, receipts, usage logs, and audit-ready
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/syamai/crypto-payer-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server