Xaurr
REMOTE · MCP.XAURR.COM
Xaurr payments for Ghana, Kenya, Uganda, Nigeria: docs, test checkouts, Payouts, invoices, links
Available components
Last scanned (20 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_test_checkout). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3747 tokens (~78/item across 48 items; 48 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 49 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
- New tool “books_add_bill” functional
- New tool “books_add_entry” functional
- 15 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_api_reference” rewrote its description, which is the text the model reads security
- Schema quality: 2799 → 3408 ▼ functional
- New tool “books_balance_sheet” functional
- New tool “books_cash_flow” functional
- New tool “books_check” functional
- New tool “books_entries” functional
- New tool “books_money_owed” functional
- New tool “books_profit_and_loss” functional
- New tool “books_vat” functional
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +5
- Tool “create_invoice” rewrote its description, which is the text the model reads security
- Tool “create_payment_link” rewrote its description, which is the text the model reads security
- Tool “mark_invoice_paid” rewrote its description, which is the text the model reads security
- Tool “payouts_collect” rewrote its description, which is the text the model reads security
- Tool “platform_earnings” rewrote its description, which is the text the model reads security
- Tool “platform_operators” rewrote its description, which is the text the model reads security
- Tool “send_test_webhook” rewrote its description, which is the text the model reads security
- Schema quality: 54 → 71 ▼ functional
- Tool coverage: 18% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fair → good functional
- “create_invoice” reworded the description of “client_email” cosmetic
- “create_invoice” reworded the description of “client_name” cosmetic
- “create_invoice” reworded the description of “client_phone” cosmetic
- “create_invoice” reworded the description of “currency” cosmetic
- “create_invoice” reworded the description of “items” cosmetic
- “create_invoice” reworded the description of “notes” cosmetic
- “create_payment_link” reworded the description of “currency” cosmetic
- “create_payment_link” reworded the description of “description” cosmetic
- “create_payment_link” reworded the description of “ships_goods” cosmetic
- “create_payment_link” reworded the description of “title” cosmetic
- “create_test_checkout” reworded the description of “cancelUrl” cosmetic
- “create_test_checkout” reworded the description of “currency” cosmetic
- “create_test_checkout” reworded the description of “title” cosmetic
- “explain_error” reworded the description of “message” cosmetic
- “get_api_reference” reworded the description of “section” cosmetic
- “get_checkout” reworded the description of “reference” cosmetic
- “get_payment” reworded the description of “receipt” cosmetic
- “integration_example” reworded the description of “stack” cosmetic
- “list_invoices” reworded the description of “limit” cosmetic
- “list_invoices” reworded the description of “status” cosmetic
- “list_payment_links” reworded the description of “limit” cosmetic
- “list_payments” reworded the description of “limit” cosmetic
- “mark_invoice_paid” reworded the description of “invoice_id” cosmetic
- “pay_test_checkout” reworded the description of “outcome” cosmetic
- “pay_test_checkout” reworded the description of “reference” cosmetic
- “payout_collection_methods” reworded the description of “currency” cosmetic
- “payouts_add_worker” reworded the description of “currency” cosmetic
- “payouts_add_worker” reworded the description of “email” cosmetic
- “payouts_add_worker” reworded the description of “name” cosmetic
- “payouts_add_worker” reworded the description of “phone” cosmetic
- “payouts_balance” reworded the description of “currency” cosmetic
- “payouts_collect” reworded the description of “amount” cosmetic
- “payouts_collect” reworded the description of “currency” cosmetic
- “payouts_collect” reworded the description of “payer_name” cosmetic
- “payouts_collect” reworded the description of “phone” cosmetic
- “payouts_collect” reworded the description of “reference” cosmetic
- “payouts_collect” reworded the description of “worker_share” cosmetic
- “payouts_credit_worker” reworded the description of “amount” cosmetic
- “payouts_credit_worker” reworded the description of “reference” cosmetic
- “payouts_credit_worker” reworded the description of “worker_id” cosmetic
- “payouts_get_collection” reworded the description of “collection_id” cosmetic
- “payouts_get_withdrawal” reworded the description of “withdrawal_id” cosmetic
- “payouts_get_worker” reworded the description of “reference” cosmetic
- “payouts_get_worker” reworded the description of “worker_id” cosmetic
- “payouts_pay_worker” reworded the description of “amount” cosmetic
- “payouts_pay_worker” reworded the description of “reference” cosmetic
- “payouts_pay_worker” reworded the description of “worker_id” cosmetic
- “payouts_test_topup” reworded the description of “amount” cosmetic
- “payouts_test_topup” reworded the description of “currency” cosmetic
- “payouts_test_topup” reworded the description of “reference” cosmetic
- “payouts_worker_history” reworded the description of “worker_id” cosmetic
- “platform_earnings” reworded the description of “currency” cosmetic
- “platform_operators” reworded the description of “status” cosmetic
- “quote_fees” reworded the description of “amount” cosmetic
- “quote_fees” reworded the description of “kind” cosmetic
- “quote_fees” reworded the description of “method” cosmetic
- “quote_fees” reworded the description of “mode” cosmetic
- “quote_fees” reworded the description of “payout_to” cosmetic
- “refund_checkout” reworded the description of “reason” cosmetic
- “refund_checkout” reworded the description of “reference” cosmetic
- “send_test_webhook” reworded the description of “webhook_id” cosmetic
- 11 Nov 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.xaurr.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=xaurr.com | CN=WE1,O=Google Trust Services,C=US | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 7ac7e53a02040e4b1304af7762ed27e2 |
| SANs: xaurr.com, mcp.xaurr.com, *.mcp.xaurr.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.xaurr.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| xaurr.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.xaurr.com | Verified | 200 | |
| http (plaintext) | http://mcp.xaurr.com | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account_readiness Am I ready for live payments? ~38
This account's own go-live checklist: what is done and what is still missing before live keys take real payments (GET /account/readiness).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
books_add_bill Add a supplier bill ~162
Record a bill from a supplier in Money owed (POST /books/bills). Nothing is paid: the business pays it itself later. The category is an expense category name as in Accounting. The business is told each time. Needs real data (live key).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | The amount, above 0. |
| bill_date | string | – | YYYY-MM-DD; today if left out. |
| category | string | yes | An expense category name as shown in Accounting. |
| currency | string | yes | 3 letters, e.g. USD. |
| description | string | – | What it is for. |
| due_date | string | – | YYYY-MM-DD, when it must be paid (optional). |
| supplier | string | yes | Who the bill is from. |
No output schema declared.
No examples provided.
books_add_entry Add an entry to the books ~177
Add one income or expense entry to the business's books (POST /books/entries), e.g. a cash sale or an expense paid. Books only: nothing is paid or sent. Use the category name exactly as in Accounting (an unknown name returns the list to choose from). The business is told each time. Needs real data (live key).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | The amount, above 0. |
| category | string | yes | The category name as shown in Accounting, e.g. Sales or Rent. |
| currency | string | yes | 3 letters, e.g. USD, GHS, KES. |
| date | string | – | YYYY-MM-DD; today if left out. |
| description | string | – | What it was, e.g. 'Office chairs'. |
| kind | string | yes | income or expense. |
No output schema declared.
No examples provided.
books_balance_sheet Balance Sheet ~63
The business's Balance Sheet on a date, per currency: assets, liabilities, equity and retained earnings (GET /books/balance-sheet). Needs real data (live key).
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | The date, YYYY-MM-DD. Leave out for today. |
No output schema declared.
No examples provided.
books_cash_flow Cash flow ~91
The business's cash flow statement for any dates, per currency: opening cash, trading, assets, loans and owner money, closing cash (GET /books/cash-flow). Needs real data (live key).
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | First day, YYYY-MM-DD. Leave out to start from the first entry. |
| to | string | – | Last day, YYYY-MM-DD. Leave out for today. |
No output schema declared.
No examples provided.
books_check Books check ~59
A quick look over the books for things to fix: costs without receipts, unusual amounts, possible duplicates, future dates, months not reconciled, accounts below zero, VAT settings (GET /books/check). Changes nothing. Needs real data (live key).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
books_entries Ledger entries ~121
Entries in the business's books, newest first, optionally for some dates or matching a word in the description or category (GET /books/entries). Needs real data (live key).
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | First day, YYYY-MM-DD. Leave out to start from the first entry. |
| limit | number | – | How many entries to return (1 to 200, default 50). |
| search | string | – | Only entries whose description or category contains this. |
| to | string | – | Last day, YYYY-MM-DD. Leave out for today. |
No output schema declared.
No examples provided.
books_money_owed Money owed ~53
Who owes the business (unpaid invoices) and what it owes (unpaid bills), with how late each is and totals by age (GET /books/money-owed). Needs real data (live key).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
books_profit_and_loss Profit & Loss ~97
The business's Profit & Loss for any dates, per currency: income and costs by category, totals and profit (GET /books/profit-and-loss). The same figures as Accounting in the app. Needs real data (live key).
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | First day, YYYY-MM-DD. Leave out to start from the first entry. |
| to | string | – | Last day, YYYY-MM-DD. Leave out for today. |
No output schema declared.
No examples provided.
books_vat VAT summary (Ghana) ~99
VAT on sales and purchases and the VAT to pay GRA for any dates, split into VAT, NHIL and GETFund (GET /books/vat). For checking only: confirm with an accountant before filing. Needs real data (live key).
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | First day, YYYY-MM-DD. Leave out to start from the first entry. |
| to | string | – | Last day, YYYY-MM-DD. Leave out for today. |
No output schema declared.
No examples provided.
check_platform_connection Check an operator's platform code ~49
Xaurr Connect: with the OPERATOR's test key, check they are connected to your platform (GET /platform-connection).
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | yes | Your platform code, PLT-... |
No output schema declared.
No examples provided.
create_invoice Create an invoice ~142
Create an invoice document (POST /invoices), the same as Create Invoice in the app. Needs a LIVE key: invoices are real documents.
| Name | Type | Req | Description |
|---|---|---|---|
| client_email | string | – | The client's email address (optional). |
| client_name | string | yes | The client's name. |
| client_phone | string | – | The client's phone number (optional). |
| currency | string | yes | Currency of the invoice: GHS, KES, UGX, NGN or USD. |
| due_date | string | – | YYYY-MM-DD |
| items | array | yes | The invoice lines, 1 to 50. |
| notes | string | – | Notes printed on the invoice (optional). |
No output schema declared.
No examples provided.
create_payment_link Create a payment link ~135
Create a reusable payment link (POST /payment-links), paid into your own account in the currency's country. Test key = test link; live key = a real link to share.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number|null | – | Fixed price, or null to let the payer choose. |
| currency | string | yes | Currency of the link: GHS, KES, UGX, NGN or USD. |
| description | string | – | More detail shown to the payer (optional). |
| ships_goods | boolean | – | true when goods are delivered after payment. |
| title | string | yes | Name of the link, shown to the payer. |
No output schema declared.
No examples provided.
create_test_checkout Create a test checkout ~202
Create a TEST hosted checkout (POST /checkout-sessions) and return its pay url. Needs a test key with write permission.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | The total, at most 2 decimals. |
| cancelUrl | string | – | Where the customer goes if they cancel: https://, or http://localhost while testing. |
| currency | string | yes | Currency of the account's country: GHS (Ghana), KES (Kenya), UGX (Uganda) or NGN (Nigeria). |
| platform | string | – | Platforms only: your platform code (PLT-...). |
| platformFee | number | – | Platforms only: your own fee on this sale. |
| reference | string | yes | Your order number, 1-64 characters. |
| successUrl | string | yes | https:// (or http://localhost) return address. |
| title | string | – | Short name of the order, shown to the customer on the checkout page. |
No output schema declared.
No examples provided.
explain_error Explain a Xaurr error ~42
Explain an error message returned by the Xaurr API and how to fix it.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The error text exactly as the Xaurr API returned it. |
No output schema declared.
No examples provided.
get_api_reference API reference section ~67
The full reference for one part of the API. Sections: authentication, checkout-sessions, get-checkout, payments, quote, connect, payouts, links-invoices, books, webhooks, embed, countries.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | yes | Which part of the API reference to return. |
No output schema declared.
No examples provided.
get_checkout Look up a checkout ~45
Status of one checkout by your own order reference (GET /checkout-sessions/:reference).
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | Your own order reference, as sent when the checkout was created. |
No output schema declared.
No examples provided.
get_openapi OpenAPI description ~35
Where to download the machine-readable OpenAPI 3.1 description of the Xaurr API, for code generators and API tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_payment Look up a payment ~37
One payment by its receipt number (GET /payments/:receipt).
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | string | yes | The payment receipt number, for example TX-.... |
No output schema declared.
No examples provided.
go_live_checklist Go-live checklist ~20
What is needed before live keys take real payments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
integration_example Integration example ~64
Tested starting code to create a Xaurr checkout from a server, or to verify a webhook. Stacks: node, nextjs, laravel, php, django, flutter, wordpress, webhook.
| Name | Type | Req | Description |
|---|---|---|---|
| stack | string | yes | The language or framework the example is written for. |
No output schema declared.
No examples provided.
list_invoices My invoices ~83
Your invoices, newest first, optionally only unpaid or paid (GET /invoices). Shows which are overdue. Needs a LIVE key: invoices are real documents.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many invoices to return, newest first (1 to 100, default 20). |
| status | string | – | Only unpaid or only paid invoices. Leave out for all. |
No output schema declared.
No examples provided.
list_payment_links My payment links ~55
Your payment links for the key's environment, with how many times each was paid (GET /payment-links).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many links to return, newest first (1 to 100, default 20). |
No output schema declared.
No examples provided.
list_payments List test payments ~46
The most recent test payments on the account (GET /payments).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many payments to return, newest first (1 to 50, default 10). |
No output schema declared.
No examples provided.
list_webhooks Webhooks and recent deliveries ~30
Your test webhooks and their last 10 deliveries (GET /webhooks). No secrets are shown.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mark_invoice_paid Mark an invoice paid ~49
Mark one of your invoices paid (POST /invoices/:id/mark-paid); it is also recorded in bookkeeping. Needs a LIVE key.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | The invoice id. |
No output schema declared.
No examples provided.
pay_test_checkout Pay a test checkout ~88
Pay (or fail) a TEST checkout with the right sandbox test number for its country and payout speed, like a customer would, so you see real statuses and webhooks without a phone. Ghana, Kenya and Uganda.
| Name | Type | Req | Description |
|---|---|---|---|
| outcome | string | – | success pays the checkout; fail makes the payment fail. Default success. |
| reference | string | yes | Your own order reference of the test checkout. |
No output schema declared.
No examples provided.
payout_collection_methods Ways to pay in a country ~71
Xaurr Payouts: the ways a customer can pay in one currency's country (GET /collections/methods).
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | Currency of the account's country: GHS (Ghana), KES (Kenya), UGX (Uganda) or NGN (Nigeria). |
No output schema declared.
No examples provided.
payouts_add_worker Add a worker ~133
Xaurr Payouts: add a test worker (POST /workers). Returns their onboarding_url.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency of the account's country: GHS (Ghana), KES (Kenya), UGX (Uganda) or NGN (Nigeria). |
| string | – | The worker's email address (optional). | |
| name | string | yes | The worker's full name, as on their ID. |
| phone | string | – | The worker's Mobile Money number with country code, for example 256772123456. |
| reference | string | yes | Your own id for them. |
No output schema declared.
No examples provided.
payouts_balance Xaurr Payouts test balance ~43
Xaurr Payouts: your test balance (GET /balance), optionally for one currency.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Only this currency. Leave out for every currency. |
No output schema declared.
No examples provided.
payouts_collect Collect a payment into Payouts ~166
Xaurr Payouts: ask a customer to pay into your balance by Mobile Money (POST /collections). Test mode uses the Xaurr test numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount the customer pays, in the chosen currency. |
| currency | string | yes | Currency of the account's country: GHS (Ghana), KES (Kenya), UGX (Uganda) or NGN (Nigeria). |
| payer_name | string | – | The customer's name (optional). |
| phone | string | yes | The customer's Mobile Money number with country code. |
| reference | string | yes | Your own unique reference for this collection. |
| worker | string | – | Optional worker id to credit a share. |
| worker_share | number | – | Part of the amount credited to that worker (optional). |
No output schema declared.
No examples provided.
payouts_credit_worker Credit a worker ~82
Xaurr Payouts: credit a worker's earnings from your balance (POST /workers/:id/earnings).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to credit, in the worker's currency. |
| reference | string | yes | Your own unique reference for this credit. |
| worker_id | string | yes | The worker id Xaurr returned when the worker was added. |
No output schema declared.
No examples provided.
payouts_get_collection A collection's status ~45
Xaurr Payouts: one collection's status (GET /collections/:id).
| Name | Type | Req | Description |
|---|---|---|---|
| collection_id | string | yes | The collection id Xaurr returned when the collection was made. |
No output schema declared.
No examples provided.
payouts_get_withdrawal A payout's status ~57
Xaurr Payouts: one payout's status (GET /withdrawals/:id): queued, paid, returned or needs_review.
| Name | Type | Req | Description |
|---|---|---|---|
| withdrawal_id | string | yes | The payout id Xaurr returned when the payout was made. |
No output schema declared.
No examples provided.
payouts_get_worker Look up a worker ~79
Xaurr Payouts: one worker's status, by their id or by your own reference (GET /workers/:id or /workers?reference=).
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | – | Your own reference for the worker, used instead of worker_id. |
| worker_id | string | – | The worker id Xaurr returned when the worker was added. |
No output schema declared.
No examples provided.
payouts_pay_worker Pay a worker ~86
Xaurr Payouts: pay a worker out of their earnings (POST /workers/:id/withdrawals). Test money only.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to pay out, in the worker's currency. |
| reference | string | yes | Your own unique reference for this payout. |
| worker_id | string | yes | The worker id Xaurr returned when the worker was added. |
No output schema declared.
No examples provided.
payouts_test_topup Add test money to Payouts ~100
Xaurr Payouts: add TEST money to your balance (POST /balance/test-topup).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Test money to add, in the chosen currency. |
| currency | string | yes | Currency of the account's country: GHS (Ghana), KES (Kenya), UGX (Uganda) or NGN (Nigeria). |
| reference | string | – | Your own unique reference for this top-up (optional). |
No output schema declared.
No examples provided.
payouts_worker_history A worker's history ~48
Xaurr Payouts: one worker's earnings and payouts (GET /workers/:id/history).
| Name | Type | Req | Description |
|---|---|---|---|
| worker_id | string | yes | The worker id Xaurr returned when the worker was added. |
No output schema declared.
No examples provided.
platform_earnings My platform's earnings ~62
Platforms (Xaurr Connect): your fee earnings per currency and the latest ones, for the key's environment (GET /platform/earnings). Needs the platform's own key.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Only this currency. Leave out for every currency. |
No output schema declared.
No examples provided.
platform_operators My platform's operators ~67
Platforms (Xaurr Connect): every operator connected to your platform, with country, agreed maximum fee and whether they can take live payments (GET /platform/operators). Needs the platform's own live key.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Only active or only disconnected operators. Leave out for all. |
No output schema declared.
No examples provided.
quote_fees Fee quote ~121
What a payment costs in Ghana cedis (GET /quote): what the customer pays, the fees, and what you receive.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount in Ghana cedis. |
| kind | string | – | What the payment is for. in_app is a normal sale; plugin is a website checkout. |
| method | string | – | How the customer pays. |
| mode | string | – | receive: the amount you want to receive. charge: the amount the customer pays. |
| payout_to | string | – | Where the money is paid out to. |
No output schema declared.
No examples provided.
refund_checkout Refund a test checkout ~62
Ask for a refund of a paid TEST checkout (POST /checkout-sessions/:reference/refund).
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | Why it is refunded (optional, kept with the refund). |
| reference | string | yes | Your own order reference of the paid test checkout. |
No output schema declared.
No examples provided.
sales_summary How much did I make? ~58
Money received and sent in the last N days, per currency, completed only (GET /summary). Test key = test money; live key = real money.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | 7 for this week, 30 for this month. |
No output schema declared.
No examples provided.
search_docs Search the Xaurr docs ~50
Answer a question about the Xaurr API from the official docs (checkouts, fees, Connect, Payouts, webhooks, countries).
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question, in plain words. |
No output schema declared.
No examples provided.
send_test_webhook Send a test webhook ~64
Send a signed test.ping to one of your test webhooks (POST /webhooks/:id/test). Each delivery carries an X-Xaurr-Signature header to verify.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | The id of one of your test webhooks. |
No output schema declared.
No examples provided.
test_values Test numbers ~28
The phone numbers and values that complete or fail test payments and payouts, per country and payout speed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
waiting_payouts What is waiting to be paid out ~45
Sales waiting for your payout schedule, the payout fee and what you will receive (GET /payouts/waiting). Needs a LIVE key: this is real money.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whats_new What's new in the API ~19
Recent changes to the Xaurr API, newest first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Xaurr MCP server?
Xaurr is a hosted endpoint at https://mcp.xaurr.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.xaurr.com
claude mcp add --transport http com-xaurr-mcp 'https://mcp.xaurr.com/'
What is the Xaurr MCP server?
Xaurr is an MCP server listed in the public MCP registry as com.xaurr/mcp. Xaurr payments for Ghana, Kenya, Uganda, Nigeria: docs, test checkouts, Payouts, invoices, links. This page covers its hosted endpoint (https://mcp.xaurr.com).
Is the Xaurr MCP server safe to use?
Xaurr scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Xaurr MCP server expose?
Xaurr exposes 48 tools: search_docs, get_api_reference, integration_example, explain_error, test_values, and 43 more. Their descriptions and schemas cost roughly 3,635 tokens of context every time the server is loaded.
Does the Xaurr MCP server require authentication?
No. We connected to Xaurr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Xaurr MCP server still maintained?
Xaurr is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Xaurr MCP server?
VerifyMCP ran 12 checks on Xaurr, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Xaurr: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.