WariMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | Yes | PostgreSQL connection string (e.g. postgresql://warimcp:pass@localhost:5432/warimcp) | |
| HUB2_API_KEY | No | Hub2 API key (secondary aggregator) | |
| WARIMCP_MODE | No | Mode: mock, sandbox, or live | mock |
| WARIMCP_PORT | No | HTTP port when using http or both transport | 3000 |
| WAVE_API_KEY | No | Wave API key | |
| PAPSS_API_KEY | No | PAPSS API key | |
| KKIAPAY_SECRET | No | KKiaPay secret | |
| CINETPAY_API_KEY | No | CinetPay API key | |
| CINETPAY_SITE_ID | No | CinetPay site ID | |
| MTN_MOMO_API_KEY | No | MTN MoMo API key | |
| MTN_MOMO_API_USER | No | MTN MoMo API user | |
| WARIMCP_TRANSPORT | No | Transport: stdio, http, or both | both |
| FEDAPAY_PUBLIC_KEY | No | FedaPay public key | |
| FEDAPAY_SECRET_KEY | No | FedaPay secret key (primary aggregator) | |
| KKIAPAY_PUBLIC_KEY | No | KKiaPay public key | |
| MONEROO_SECRET_KEY | No | Moneroo secret key | |
| KKIAPAY_PRIVATE_KEY | No | KKiaPay private key | |
| WAVE_WEBHOOK_SECRET | No | Wave webhook secret | |
| MTN_MOMO_ENVIRONMENT | No | MTN MoMo environment (sandbox or production) | sandbox |
| WARIMCP_RELAY_SECRET | No | Secret for HMAC-signed webhook relay | |
| MTN_MOMO_CALLBACK_URL | No | MTN MoMo callback URL | |
| FLUTTERWAVE_PUBLIC_KEY | No | Flutterwave public key | |
| FLUTTERWAVE_SECRET_KEY | No | Flutterwave secret key | |
| WARIMCP_WEBHOOK_BASE_URL | No | Base URL for webhook relay | |
| MTN_MOMO_COLLECTION_SUBSCRIPTION_KEY | No | MTN MoMo collection subscription key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_providersA | List all WariMCP payment providers, their configuration status, and supported rails |
| initiate_paymentC | Initiate a payment through any configured WariMCP provider. Returns a checkout URL for the customer. |
| verify_paymentB | Check the status of a payment transaction |
| refund_paymentB | Issue a refund for a completed payment transaction |
| list_transactionsB | List recent payment transactions with optional filters |
| generate_payment_linkC | Generate a shareable payment link for a customer |
| initiate_payoutA | Disburse funds to a mobile money wallet or bank account (seller payouts) |
| verify_payoutA | Check the status of a payout |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Tools are mostly distinct, but initiate_payment and generate_payment_link both create payment flows, which could cause confusion. Other tools (verify, refund, list, payout) are clearly separated.
All tools follow a consistent verb_noun pattern with clear verbs (list, initiate, verify, refund, generate) and nouns (providers, payment, link, payout, transactions). No mixed conventions.
8 tools is well-scoped for a payments server, covering payment and payout operations without unnecessary bloat.
The server covers the main payment lifecycle (initiate, verify, refund, list) and payout lifecycle (initiate, verify). Missing a dedicated single-transaction retrieval or cancel operation, but these can be worked around with list/verify.