Ultraner MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ULTRANER_API_KEY | Yes | Your secret API key | |
| ULTRANER_BASE_URL | No | Optional base URL override | https://api.ultraner.com |
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 |
|---|---|
| get_supported_countriesA | Every market Ultraner knows about, whether it is live, its currency, and the provider code to send for each mobile-money network there. Needs no API key. |
| get_supported_currenciesA | Every settlement currency, how many decimal places it has, and which countries share it. Read this before constructing an amount: most African currencies have no minor unit and are sent as whole numbers. |
| get_payment_networksB | Every mobile-money brand, the markets it reaches, and the provider codes that select it. Includes the brands that are NOT available, so they are not assumed. |
| get_capabilitiesB | What Ultraner can do (collect, disburse, settle, escrow, subscriptions, FX and the rest), each with its status, whether it varies by market, and any caveat. |
| get_use_casesA | Common jobs businesses do with Ultraner, and which capabilities each one needs. Useful for turning "I am building a marketplace" into the right set of calls. |
| get_corridorsA | Which markets can pay which, whether a rate is applied, and whether the two ends use different minor units. Capability only: quote a specific corridor through the API before relying on it. |
| get_walletB | Get Ultraner wallet balances. |
| get_payment_statusC | Check a payment by its Ultraner reference. |
| list_transactionsD | List recent transactions. |
| create_mobile_money_paymentA | Charge an African mobile-money wallet (M-Pesa, Airtel, MTN, Mixx by Yas and the rest). Call get_supported_countries first for the provider code, and get_supported_currencies for whether the amount is whole units or cents. |
| create_disbursementB | Pay money out to a mobile wallet. Needs ULTRANER_SIGNATURE_KEY, because the API requires a signature naming the person authorising the withdrawal. Live in fewer markets than collection: check get_capabilities. |
| create_checkout_sessionA | Mint a one-time, expiring Ultraner checkout token. Returns a token, a hosted url and an embed url; the payer picks mobile money, card or PayPal on the hosted page. The equivalent of Stripe checkout.sessions.create. |
| create_paypal_orderC | Create a PayPal order for international payers. |
| create_stripe_sessionC | Create a Stripe checkout session for card payments. |
| create_escrowB | Hold funds until released. The money is taken from the payer and held rather than forwarded, so neither side has to go first. |
| release_escrowA | Release an escrow hold to its recipient. This moves money and cannot be undone by the same call. |
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 16 tools
Each tool targets a distinct resource or action, and descriptions clarify boundaries. There is minor potential overlap between create_checkout_session and create_stripe_session/create_paypal_order, but overall selection is clear.
All tool names use snake_case with a consistent verb_noun pattern (get_, list_, create_, release_). No mixed conventions or vague verbs.
16 tools is slightly above the typical 3-15 range but each maps to a distinct capability; the set is comprehensive without excessive redundancy.
Core collection, disbursement, escrow, and wallet operations are covered, but advertised capabilities like subscriptions, FX, and settlement lack dedicated tools. Refunds, cancellations, and transaction detail are also missing, creating dead ends.